<?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 Use of predict command for alerting in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505683#M141376</link>
    <description>&lt;P&gt;Well , I want to create an alert which alert me whenever there is spike in Errors. Currently we are comparing say past 30m count with last 2 week same time same date and comparing with 2w average. But I want to create a near real time alert as it can be false positive this way.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My errors are like some are trending some come only at time of issues and some are like more during peak business hours and less during off business hours but I want to capture the real spikes like avoiding it to trigger when we move from non business to business hours. I was hoping if I can use predict command to do that but not clear with all algos and if that is right thing to use here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=rxc sourcetype="rxcapp" (level=ERROR) earliest=-30m@m latest=@m|rex "Id:\s*(?&amp;lt;Id&amp;gt;\d+)," | search  [| inputlookup abc.csv | rename id as Id | fields Id]| lookup abc.csv id As Id OUTPUT site|bucket _time span=5m| stats count by _time error_msg site| predict lower95=lower upper95=upper algorithm=LLP5 count as predict| where count&amp;gt;'upper(predict)'|stats latest(count) by error_msg site&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;will this be helpful or this is wrong ? Can predict be used this way with stats command ?or any other suggestion on approach.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jun 2020 09:01:04 GMT</pubDate>
    <dc:creator>ksharma7</dc:creator>
    <dc:date>2020-06-23T09:01:04Z</dc:date>
    <item>
      <title>Use of predict command for alerting</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505683#M141376</link>
      <description>&lt;P&gt;Well , I want to create an alert which alert me whenever there is spike in Errors. Currently we are comparing say past 30m count with last 2 week same time same date and comparing with 2w average. But I want to create a near real time alert as it can be false positive this way.&amp;nbsp;&lt;/P&gt;&lt;P&gt;My errors are like some are trending some come only at time of issues and some are like more during peak business hours and less during off business hours but I want to capture the real spikes like avoiding it to trigger when we move from non business to business hours. I was hoping if I can use predict command to do that but not clear with all algos and if that is right thing to use here.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=rxc sourcetype="rxcapp" (level=ERROR) earliest=-30m@m latest=@m|rex "Id:\s*(?&amp;lt;Id&amp;gt;\d+)," | search  [| inputlookup abc.csv | rename id as Id | fields Id]| lookup abc.csv id As Id OUTPUT site|bucket _time span=5m| stats count by _time error_msg site| predict lower95=lower upper95=upper algorithm=LLP5 count as predict| where count&amp;gt;'upper(predict)'|stats latest(count) by error_msg site&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;will this be helpful or this is wrong ? Can predict be used this way with stats command ?or any other suggestion on approach.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 09:01:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505683#M141376</guid>
      <dc:creator>ksharma7</dc:creator>
      <dc:date>2020-06-23T09:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: Use of predict command for alerting</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505819#M141431</link>
      <description>&lt;P&gt;I'm skeptical that &lt;STRONG&gt;predict&lt;/STRONG&gt; would be the right way to do that.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems like the right thing to do would be, each night off peak, to calculate the next day's boundaries &lt;EM&gt;once&lt;/EM&gt;&amp;nbsp; for each 5, 10 or 15 minute increment, and output those times and limits to a lookup table.&lt;/P&gt;&lt;P&gt;Then, you'd just have to calculate the current errors and read the lookup table to get the limits for whatever &lt;STRONG&gt;_time&lt;/STRONG&gt; and &lt;STRONG&gt;site&lt;/STRONG&gt;&amp;nbsp;you are running and test the compliance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 19:07:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505819#M141431</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2020-06-23T19:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Use of predict command for alerting</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505869#M141494</link>
      <description>&lt;P&gt;Yeah , then I think it is good the way I am using it currently like comparing with two week average count&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 05:05:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Use-of-predict-command-for-alerting/m-p/505869#M141494</guid>
      <dc:creator>ksharma7</dc:creator>
      <dc:date>2020-06-24T05:05:41Z</dc:date>
    </item>
  </channel>
</rss>

