<?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: Email alert not triggering in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180534#M3045</link>
    <description>&lt;P&gt;Yes, "/5" works.&lt;/P&gt;</description>
    <pubDate>Wed, 06 May 2015 15:23:45 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-05-06T15:23:45Z</dc:date>
    <item>
      <title>Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180526#M3037</link>
      <description>&lt;P&gt;Hi I need help with my email alerts.&lt;/P&gt;

&lt;P&gt;I basically need to have an email alerting me that one of my process which I am logging is taking more than 2 hours or x hours.&lt;/P&gt;

&lt;P&gt;So I have the basic query set up and let's say it is QUERY. &lt;/P&gt;

&lt;P&gt;I've made the following alert from the following query:&lt;/P&gt;

&lt;P&gt;QUERY | eval result=if(x&amp;gt;2,"YES","NO") | table result&lt;BR /&gt;
where x is the current time since the process started (in hours).&lt;/P&gt;

&lt;P&gt;I then saved this query as an alert and used the following settings:&lt;BR /&gt;
Alert type: real time&lt;BR /&gt;
Trigger condition: custom&lt;BR /&gt;
Custom condition: search result=YES&lt;BR /&gt;
in: 2 day(s)&lt;/P&gt;

&lt;P&gt;I verified that the search query:&lt;/P&gt;

&lt;P&gt;QUERY | eval result=if(x&amp;gt;2,"YES","NO") | table result | search result=YES&lt;/P&gt;

&lt;P&gt;gives me a result if the time taken is more than 2 hours however it doesn't trigger an email alert.&lt;/P&gt;

&lt;P&gt;Anyone can give me an idea of what I did wrong or where I can go from here? &lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2015 11:59:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180526#M3037</guid>
      <dc:creator>twiggle</dc:creator>
      <dc:date>2015-05-05T11:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180527#M3038</link>
      <description>&lt;P&gt;Try with == instead of =, I'm not sure if this will help?&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2015 13:11:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180527#M3038</guid>
      <dc:creator>MichaelPriest</dc:creator>
      <dc:date>2015-05-05T13:11:17Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180528#M3039</link>
      <description>&lt;P&gt;Are you verifying the search in real-time the same way you are scheduling it? I wonder if real-time can't keep track that far out.&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2015 14:21:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180528#M3039</guid>
      <dc:creator>jeremiahc4</dc:creator>
      <dc:date>2015-05-05T14:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180529#M3040</link>
      <description>&lt;P&gt;First of all, unless you deliberately engineered your Splunk cluster for RealTime searches, DO NOT USE THEM; you will destroy performance on your entire cluster.   I would run your search instead every 5 or 10 minutes over the last X hours.  Next, I would use "QUERY | where x&amp;gt;2" and then use trigger conditions for "number of results &amp;gt; 0".&lt;/P&gt;</description>
      <pubDate>Tue, 05 May 2015 15:31:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180529#M3040</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-05T15:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180530#M3041</link>
      <description>&lt;P&gt;How do you get it to search every 5 or 10 minutes? &lt;/P&gt;

&lt;P&gt;I looked at the schedule alert type and under the 'Time Range' there's only 'Run every hour', '.. Day', '... Week' etc.&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2015 08:13:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180530#M3041</guid>
      <dc:creator>twiggle</dc:creator>
      <dc:date>2015-05-06T08:13:10Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180531#M3042</link>
      <description>&lt;P&gt;Yes that's what I did to verify it. I did it that way as I read that the custom condition applies the query that you insert above the base query.&lt;/P&gt;

&lt;P&gt;Which in this case is: QUERY | eval result=if(x&amp;gt;2,"YES","NO") | table result&lt;/P&gt;

&lt;P&gt;I did ensure that the real-time search looks at records beyond 2 hours. &lt;/P&gt;

&lt;P&gt;I'll look into what @woodcock mentioned. That seems to be a better alternative.&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2015 08:17:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180531#M3042</guid>
      <dc:creator>twiggle</dc:creator>
      <dc:date>2015-05-06T08:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180532#M3043</link>
      <description>&lt;P&gt;Nope, that didn't do the trick.&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2015 08:48:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180532#M3043</guid>
      <dc:creator>twiggle</dc:creator>
      <dc:date>2015-05-06T08:48:18Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180533#M3044</link>
      <description>&lt;P&gt;Ah ok, using the cron notation for scheduled alerts right? &lt;/P&gt;

&lt;P&gt;*/5 * * * * or */10 * * * *&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2015 08:49:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180533#M3044</guid>
      <dc:creator>twiggle</dc:creator>
      <dc:date>2015-05-06T08:49:52Z</dc:date>
    </item>
    <item>
      <title>Re: Email alert not triggering</title>
      <link>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180534#M3045</link>
      <description>&lt;P&gt;Yes, "/5" works.&lt;/P&gt;</description>
      <pubDate>Wed, 06 May 2015 15:23:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Email-alert-not-triggering/m-p/180534#M3045</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-06T15:23:45Z</dc:date>
    </item>
  </channel>
</rss>

