Dashboards & Visualizations

Not running search

nithys
Communicator

Hi

I am adding the query to my dashboard and when i click on highlighted run search  it is not taking to the search one.
 after index and source the keyword search is *word:is:info:name:in:data:invok*..Not sure why it is not taking to search page Screenshot 2025-03-07 at 10.47.32 PM.png

Labels (1)
0 Karma

woodcock
Esteemed Legend

I still am completely confused.  Why don't you forget XML and just describe the UI controls, and give some examles of what inputs you would use and how it would effect the searches produced.

isoutamo
SplunkTrust
SplunkTrust
Hi
I’m thinking this is just shortcut to test your written search and it works just like copy&paste your query into another window. If you want to fulfill your “tokens” etc into that query then you must run it from dashboard not from this edit mode. I haven’t DS on my hand to test it now, but you could do it easily by yourself.
r. Ismo
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @nithys ,

let me understand: isthe issue that clicking on Run search your search doesn't start or that it doesn't run (no results)?

if the first case, please try to copy the search in a search dashboard and check if it runs.

if the issue is that you search doesn't run, debug it in a search dashboard.

What does it happen if you run your search without the where condition?

Ciao.

Giuseppe

0 Karma

nithys
Communicator

It will work if i give the keyword as *init:data:invoke* runs in dashboard and also in the search of Edit search part.
but if i run *name:init:data:invoke*  it runs in dashboard but not in particular Edit search
if it is  *$entityToken:init:data:invoke* not running in dashboard nor in particular Edit search

0 Karma

nithys
Communicator

 

My source is like below i want whatever "$entityToken$" value=name is ,i want it to assign to the keyword also in *$entityToken$:init:data:invoke*

ex 
  ("/a/b/api-data-$stageToken$-name") *name:init:data:invoke*

<query>index=* source IN                ("/a/b/api-data-$stageToken$-$entityToken$") *$entityToken$:init:data:invoke*
| eval identifier=coalesce('queryParams.identifier',
'event.queryStringParameters.identifier')
| eval msg=coalesce(msg, null)
| where isnotnull(identifier) and isnotnull(msg)
| stats count</query>

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...