<?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: Alerts not working in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288855#M5320</link>
    <description>&lt;P&gt;Can you mention the search and the alert conditions you have configured, so that it's easier to find the solution.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Jan 2018 09:43:22 GMT</pubDate>
    <dc:creator>MousumiChowdhur</dc:creator>
    <dc:date>2018-01-05T09:43:22Z</dc:date>
    <item>
      <title>Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288852#M5317</link>
      <description>&lt;P&gt;I have enabled few alerts and these are the criterias:&lt;/P&gt;

&lt;P&gt;Alert Type: Scheduled by CRON&lt;BR /&gt;
Time Range: 24 Hours&lt;BR /&gt;
Cron Expression: * */4 * * *&lt;/P&gt;

&lt;P&gt;So as per this expression:  The search query will run every 4 hour for the last 24 hours and trigger alerts. (Mail in my case)&lt;/P&gt;

&lt;P&gt;Last day my search event count was 350. So why it didnt trigger after it crossed the 120 mark?&lt;/P&gt;

&lt;P&gt;Can any one help me on this?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:01:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288852#M5317</guid>
      <dc:creator>ridutta</dc:creator>
      <dc:date>2018-01-05T09:01:07Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288853#M5318</link>
      <description>&lt;P&gt;Hi! Can you please modify your cron expression with &lt;CODE&gt;0 */4 * * *&lt;/CODE&gt; and check if that's working?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:34:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288853#M5318</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-05T09:34:10Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288854#M5319</link>
      <description>&lt;P&gt;My cron expression is that only "0 */4 * * *"... but its not working. there is someting with this portal... However the suggested one is my cron expression.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:36:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288854#M5319</guid>
      <dc:creator>ridutta</dc:creator>
      <dc:date>2018-01-05T09:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288855#M5320</link>
      <description>&lt;P&gt;Can you mention the search and the alert conditions you have configured, so that it's easier to find the solution.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:43:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288855#M5320</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-05T09:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288856#M5321</link>
      <description>&lt;P&gt;Current Search Query:&lt;BR /&gt;
(index=mesb "Status_&lt;EM&gt;c=ERROR") source="*/mule-app-csone_logging_v2.0-v201712091010.log"  Attribute_1&lt;/EM&gt;&lt;EM&gt;c=CM_ROLE_UNAVAILABLE | eval _time=strptime(CreatedDate, "%Y-%m-%dT%H:%M:%S.%3N%Z") | timechart  span=1h count by Attribute_1&lt;/EM&gt;_c&lt;/P&gt;

&lt;P&gt;Should I change to :&lt;BR /&gt;
(index=mesb "Status_&lt;EM&gt;c=ERROR") source="*/mule-app-csone_logging_v2.0-v201712091010.log"  Attribute_1&lt;/EM&gt;&lt;EM&gt;c=CM_ROLE_UNAVAILABLE | timechart  span=1h count by Attribute_1&lt;/EM&gt;_c??&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 17:29:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288856#M5321</guid>
      <dc:creator>ridutta</dc:creator>
      <dc:date>2020-09-29T17:29:54Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288857#M5322</link>
      <description>&lt;P&gt;Yes, you should try the 2nd search, set the alert and check.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 09:55:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288857#M5322</guid>
      <dc:creator>MousumiChowdhur</dc:creator>
      <dc:date>2018-01-05T09:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: Alerts not working</title>
      <link>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288858#M5323</link>
      <description>&lt;P&gt;Can you put the search query in &lt;CODE&gt;101010&lt;/CODE&gt; sample code format? Also, are you setting any threshold on the number of results? I see from your question that &lt;CODE&gt;120&lt;/CODE&gt; is the threshold.&lt;BR /&gt;
My advice is to set the threshold in a query itself and just create an alert as it is without setting any threshold on the UI.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2018 10:09:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Alerts-not-working/m-p/288858#M5323</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-01-05T10:09:25Z</dc:date>
    </item>
  </channel>
</rss>

