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
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!

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...