Splunk Enterprise

What are the steps to perform as sanity checks after Splunk Indexer restart?

SudhaP54
Engager
 
Labels (2)
0 Karma
1 Solution

isoutamo
SplunkTrust
SplunkTrust
In distributed environment you should have MC (monitoring console) set up. Then you can use it to see that everything is ok, it also give you a warning when any peer is down or there are any issues (previously defined in MC).
r. Ismo

View solution in original post

0 Karma

isoutamo
SplunkTrust
SplunkTrust
In distributed environment you should have MC (monitoring console) set up. Then you can use it to see that everything is ok, it also give you a warning when any peer is down or there are any issues (previously defined in MC).
r. Ismo
0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

I would run some searches from the search head to make sure indexers are returning results.

Like -> index=* | dedup sourcetype, splunk_server | table sourcetype, splunk_server

Make sure the splunk_server field mentions all the indexers that you have.

Also, run search -> index=_internal -> in all-time real-time and check for the splunk_server field to make sure that all the indexers are ingesting the new data coming to Splunk as expected.

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...