Splunk Dev

Blue bar warnings

IgorB
Path Finder

How does Splunk decide on which splunkd WARNs are important enough to be displayed in the blue warning bar and which are filtered out?

For example the following message will get displayed:

01-11-2011 12:16:51.012 WARN  databasePartitionPolicy - applying indexing throttle for <indexPath> because bucket has too many tsidx files, is your splunk-optimize working?

but this one won't:

01-11-2011 13:45:41.474 WARN  databasePartitionPolicy - Handling shutdown or signal in DatabasePartitionPolicy: <indexPath>

There should be some kind of a default list of filters...

Rational - I want to create a scheduled search that will email the "important" warnings to splunk admin.

Tags (2)

yannK
Splunk Employee
Splunk Employee

The importance of messages are hardcoded, so the decision is made by the developer.

There is no list of all error messages you could use to build a lookup, so you may want to start with a simple count
ERROR / WARN / FATAL events per component.

   index=_internal source=*splunkd.log* NOT log_level=INFO NOT log_level=DEBUG 
  | chart count by component log_level

or check the dashboards on the SOS app.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...