Splunk Search

All resource graphs empty

n5zap
Explorer

I installed SoS, enabled the collection scripts, and even though the scripts run fine and data is indexed, the resource utilization graphs all say "No results found." I suspect SoS has the wrong hostname in the query. The "instance to query" has the right machine name "voodoo", the data in the index has the name voodoo, the inputs.conf file has the name voodoo, and still there is no data in the graphs. The landing page for the app shows the server's name as "voodoo.viewkeeper.org" and I suspect it is querying under the FQDN instead of the short name, which is wrong. How do I fix the broken query?

Tags (1)
0 Karma

muebel
SplunkTrust
SplunkTrust

In the lower lefthand corner of the chart panel you'll find a magnifier glass icon that will take you to exactly what splunk is searching for in that case. You'll be able to determine if it is using the FQDN there.

If it is, you can look at the dashboard source config to find out why it's using the FQDN. It might be displaying the hostname in the instance dropdown, but that can be different from the token that actually gets passed to the chart search.

These type of issues involve tracing multiple parts of the config, this is just a starting point. Let me know how it goes.

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!

[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 ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...