<?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: Splunk alert configuration based on dynamic log error/exception patterns in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-alert-configuration-based-on-dynamic-log-error-exception/m-p/96739#M5285</link>
    <description>&lt;P&gt;This sounds like something you could do with the &lt;CODE&gt;anomalies&lt;/CODE&gt; operator. It applies to a sliding window of events for which it monitors a field you define, and then assign an "unexpectedness" score to each value of that field.&lt;/P&gt;

&lt;P&gt;So if you have a windows containing 10000 events and 9000 of them have the value "foo", 999 have the value "obnoxious ozelot" and the 10000th event arrives with the value "preposterous panda", Splunk will assign a very high unexpectedness score to that since it's never been seen before in the sliding window of events. You could then use the unexpectedness in your alert conditions to trigger alerts on events that don't match any of the expected values.&lt;/P&gt;

&lt;P&gt;More information on the &lt;CODE&gt;anomalies&lt;/CODE&gt; command is available here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Anomalies"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Anomalies&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 24 Oct 2011 11:36:33 GMT</pubDate>
    <dc:creator>Ayn</dc:creator>
    <dc:date>2011-10-24T11:36:33Z</dc:date>
    <item>
      <title>Splunk alert configuration based on dynamic log error/exception patterns</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-alert-configuration-based-on-dynamic-log-error-exception/m-p/96738#M5284</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;We are using splunk for log managment and as well as alert configuration based on Exceptions/Errors threshold which works very well for static log contents.&lt;/P&gt;

&lt;P&gt;But if a new exception or error is introduced due to a new release or patch, there is no way to find out the new pattern of errors/exceptions with splunk alerting system.&lt;/P&gt;

&lt;P&gt;Is there any way that we can configure dynamic alerts based on dynamic nature of log pattern changes in terms of exceptions and erros with the help of REST API framework ?&lt;/P&gt;

&lt;P&gt;Please let me know the detail&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Saravanan&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2011 11:24:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-alert-configuration-based-on-dynamic-log-error-exception/m-p/96738#M5284</guid>
      <dc:creator>saro0710</dc:creator>
      <dc:date>2011-10-24T11:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk alert configuration based on dynamic log error/exception patterns</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-alert-configuration-based-on-dynamic-log-error-exception/m-p/96739#M5285</link>
      <description>&lt;P&gt;This sounds like something you could do with the &lt;CODE&gt;anomalies&lt;/CODE&gt; operator. It applies to a sliding window of events for which it monitors a field you define, and then assign an "unexpectedness" score to each value of that field.&lt;/P&gt;

&lt;P&gt;So if you have a windows containing 10000 events and 9000 of them have the value "foo", 999 have the value "obnoxious ozelot" and the 10000th event arrives with the value "preposterous panda", Splunk will assign a very high unexpectedness score to that since it's never been seen before in the sliding window of events. You could then use the unexpectedness in your alert conditions to trigger alerts on events that don't match any of the expected values.&lt;/P&gt;

&lt;P&gt;More information on the &lt;CODE&gt;anomalies&lt;/CODE&gt; command is available here: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Anomalies"&gt;http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Anomalies&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2011 11:36:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-alert-configuration-based-on-dynamic-log-error-exception/m-p/96739#M5285</guid>
      <dc:creator>Ayn</dc:creator>
      <dc:date>2011-10-24T11:36:33Z</dc:date>
    </item>
  </channel>
</rss>

