<?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: similar alerts have several behaviours in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64985#M903</link>
    <description>&lt;P&gt;The issue was probably the value set to 1 not recognized.  Per saved searches.conf.spec:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;alert.track = true | false | auto
* Specifies whether to track the actions triggered by this scheduled search.
* auto  - determine whether to track or not based on the tracking setting of each action, 
* do not track scheduled searches that always trigger actions.
* true  - force alert tracking.
* false - disable alert tracking for this search.
* Defaults to auto.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Tue, 25 Feb 2014 20:38:17 GMT</pubDate>
    <dc:creator>the_wolverine</dc:creator>
    <dc:date>2014-02-25T20:38:17Z</dc:date>
    <item>
      <title>similar alerts have several behaviours</title>
      <link>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64983#M901</link>
      <description>&lt;P&gt;When defining different alerts in the etc/user/admin/search/local/savedsearches.conf, some of them work and some don't.
However, searches work for all of them and list events as expected.&lt;/P&gt;

&lt;P&gt;Example that works:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[alert1]
action.email = 1
action.email.inline = 1
action.email.reportServerEnabled = 0
action.email.sendresults = 1
action.email.to = mymail@mail.com
alert.expires = 7d
alert.suppress = 0
counttype = number of events
cron_schedule = * * * * *
dispatch.earliest_time = rt-1m
dispatch.latest_time = rt-30s
enableSched = 1
quantity = 0
relation = greater than
search = (componentsc = "RCG" OR componentsc = "AS" OR componentsc = "VCS") AND actionsc = "ECPRO"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Example that does not work:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[alert2]
action.email = 1
action.email.inline = 1
action.email.reportServerEnabled = 0
action.email.sendresults = 1
action.email.to = mymail@mail.com
alert.expires = 7d
alert.suppress = 0
alert.suppress.period = 20s
alert.track = 1
alert.severity = 4
counttype = number of events
cron_schedule = * * * * *
dispatch.earliest_time = rt-1m
dispatch.latest_time = rt-30s
enableSched = 1
quantity = 0
relation = greater than
search = (componentsc = "AS" OR componentsc = "VCS" OR componentsc = "RCG") AND actionsc = "RBACA" AND (outcomesc = "001" OR outcomesc = "010")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 22 Mar 2011 23:54:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64983#M901</guid>
      <dc:creator>acalvo</dc:creator>
      <dc:date>2011-03-22T23:54:54Z</dc:date>
    </item>
    <item>
      <title>Re: similar alerts have several behaviours</title>
      <link>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64984#M902</link>
      <description>&lt;P&gt;Nevermind, the error was &lt;CODE&gt;alert.track = 1&lt;/CODE&gt;, it should be &lt;CODE&gt;alert.track = auto&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2011 19:03:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64984#M902</guid>
      <dc:creator>acalvo</dc:creator>
      <dc:date>2011-03-24T19:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: similar alerts have several behaviours</title>
      <link>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64985#M903</link>
      <description>&lt;P&gt;The issue was probably the value set to 1 not recognized.  Per saved searches.conf.spec:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;alert.track = true | false | auto
* Specifies whether to track the actions triggered by this scheduled search.
* auto  - determine whether to track or not based on the tracking setting of each action, 
* do not track scheduled searches that always trigger actions.
* true  - force alert tracking.
* false - disable alert tracking for this search.
* Defaults to auto.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 25 Feb 2014 20:38:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/similar-alerts-have-several-behaviours/m-p/64985#M903</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2014-02-25T20:38:17Z</dc:date>
    </item>
  </channel>
</rss>

