Splunk Search

How to use token value in stats group by field in Splunk dashboard

kasimanikandan
Engager

Hi Team,

I have stats group by fields as token it will change dynamically based on time selection. for example if select since 1st Jun 24 then my query will be like below.

eventtype="abc" |stats count by a,b,c 

and if select date before 1st Jun 2024 i.e 30th May 2024 i would like to have stats group by field like below.

eventtype="abc" |stats count by a,d,e

So my current implementation is putting group by field in token, token will be set based on time selection and final query would be like below.

eventtype="abc" |stats count by $groupby_field$

Now the issue is splunk dashboard says waiting for input the moment i add token input to stats groupby field.

Appreciate your suggestion/help to handle this scenario.

 

Thanks,

Mani

 

Labels (1)
Tags (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Assuming you are changing the groupby_field token in the change handler of the time selection input, which is essentially the input that is being waited for, you could also initialise the groupby_field token in an init block in SimpleXML - it is perhaps a little more complicated to do in Studio

0 Karma

kasimanikandan
Engager

@ITWhisperer didnt worked 

0 Karma

bowesmana
SplunkTrust
SplunkTrust

That sort of response is unlikely to elicit further help from anyone.

Please describe what you have done, and if possible post snippets of your token management logic in your dashboard

Get Updates on the Splunk Community!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...