<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Blue bar warnings in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Blue-bar-warnings/m-p/24379#M265</link>
    <description>&lt;P&gt;The importance of messages are hardcoded, so the decision is made by the developer.&lt;/P&gt;

&lt;P&gt;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 &lt;BR /&gt;
ERROR / WARN / FATAL events per component.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   index=_internal source=*splunkd.log* NOT log_level=INFO NOT log_level=DEBUG 
  | chart count by component log_level
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or check the dashboards on the SOS app.&lt;/P&gt;</description>
    <pubDate>Thu, 14 May 2015 17:31:22 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2015-05-14T17:31:22Z</dc:date>
    <item>
      <title>Blue bar warnings</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Blue-bar-warnings/m-p/24378#M264</link>
      <description>&lt;P&gt;How does Splunk decide on which splunkd WARNs are important enough to be displayed in the blue warning bar and which are filtered out? &lt;/P&gt;

&lt;P&gt;For example the following message will get displayed:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;01-11-2011 12:16:51.012 WARN  databasePartitionPolicy - applying indexing throttle for &amp;lt;indexPath&amp;gt; because bucket has too many tsidx files, is your splunk-optimize working?
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;but this one won't: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;01-11-2011 13:45:41.474 WARN  databasePartitionPolicy - Handling shutdown or signal in DatabasePartitionPolicy: &amp;lt;indexPath&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;There should be some kind of a default list of filters...&lt;/P&gt;

&lt;P&gt;Rational - I want to create a scheduled search that will email the "important" warnings to splunk admin. &lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2011 20:20:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Blue-bar-warnings/m-p/24378#M264</guid>
      <dc:creator>IgorB</dc:creator>
      <dc:date>2011-01-11T20:20:53Z</dc:date>
    </item>
    <item>
      <title>Re: Blue bar warnings</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Blue-bar-warnings/m-p/24379#M265</link>
      <description>&lt;P&gt;The importance of messages are hardcoded, so the decision is made by the developer.&lt;/P&gt;

&lt;P&gt;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 &lt;BR /&gt;
ERROR / WARN / FATAL events per component.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;   index=_internal source=*splunkd.log* NOT log_level=INFO NOT log_level=DEBUG 
  | chart count by component log_level
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;or check the dashboards on the SOS app.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 17:31:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Blue-bar-warnings/m-p/24379#M265</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2015-05-14T17:31:22Z</dc:date>
    </item>
  </channel>
</rss>

