Dashboards & Visualizations

Why is the token search returning "No Results Found"?

gbwilson
Path Finder

I am VERY new to Splunk. I'm attempting to create a dashboard where I can search an Application name and info about the application itself, the app servers it runs on, the databases that support the app, and the database servers that support the databases. I can get every panel to return results except for one.

index="databaseserver_temp" Application=$appservicefield$ | join Database [search index="applicationdatabase_temp"] | table Application, Database, VM, InstanceName

When I remove the token search "Application=$appservicefield$ I can view results, however they do not pertain to the one application I'm searching. But when I include the token, I get a "No results found" message. Not sure why the token isn't working for this particular search.

0 Karma
1 Solution

gbwilson
Path Finder

I actually figured out that I needed to switch my two indexes around. They were in the wrong places. Thank you for your assistance!

View solution in original post

0 Karma

gbwilson
Path Finder

I actually figured out that I needed to switch my two indexes around. They were in the wrong places. Thank you for your assistance!

0 Karma

niketn
Legend

@gbwilson, please go ahead and accept your own answer to mark this question as answered!

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
0 Karma

kmaron
Motivator

Is it possible your Application has a space in the value? If it does try changing your token to: Application=$appservicefield|s$

The |s means "wrap the value in quotes"

Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...