<?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: Setting alerts on exceptions in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41674#M516</link>
    <description>&lt;P&gt;The way I did this was to set up eventtypes.conf so that each event has an eventtype. You can then run a query:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;YourSearch NOT eventtype=*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And that will show all the events that aren't on your pre-defined list. You can toss that in a scheduled search no problem.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/eventtypesconf" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/eventtypesconf&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 10 Feb 2011 05:11:36 GMT</pubDate>
    <dc:creator>David</dc:creator>
    <dc:date>2011-02-10T05:11:36Z</dc:date>
    <item>
      <title>Setting alerts on exceptions</title>
      <link>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41673#M515</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I potentially want to set a scheduled search - where i specify the list of exceptions in the search - and if there is any new exception outside of those listed exceptions, Splunk should send an email alert.&lt;/P&gt;

&lt;P&gt;For example:
Consider, here is my list of exceptions:
"error: null pointer exception (login.class:1494)"
"error: database down exception (database.class:1594)"
"error: read PFD (readPDF.class:1694)"&lt;/P&gt;

&lt;P&gt;Now, whenever there is a new exception generated (outside of those listed above), Splunk sends me alert.&lt;/P&gt;

&lt;P&gt;Thanks for looking into this.
Usman Chaudhri&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2011 02:06:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41673#M515</guid>
      <dc:creator>usmanchaudhri</dc:creator>
      <dc:date>2011-02-10T02:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: Setting alerts on exceptions</title>
      <link>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41674#M516</link>
      <description>&lt;P&gt;The way I did this was to set up eventtypes.conf so that each event has an eventtype. You can then run a query:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;YourSearch NOT eventtype=*
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And that will show all the events that aren't on your pre-defined list. You can toss that in a scheduled search no problem.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/eventtypesconf" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/Admin/eventtypesconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2011 05:11:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41674#M516</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-02-10T05:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: Setting alerts on exceptions</title>
      <link>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41675#M517</link>
      <description>&lt;P&gt;Yeah, that's what i ended up doing. I saved a search as an eventtype, the search had the pre-defined list of events. Than i went ahead and scheduled another search and just specified eventtype!=&amp;lt; predefine list &amp;gt;. This gave me list of new events. &lt;/P&gt;

&lt;P&gt;Thank you&lt;BR /&gt;
Usman Chaudhri&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2011 07:40:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41675#M517</guid>
      <dc:creator>usmanchaudhri</dc:creator>
      <dc:date>2011-02-10T07:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: Setting alerts on exceptions</title>
      <link>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41676#M518</link>
      <description>&lt;P&gt;That sounds like a good solution. For my use case, we had a relatively small number of events (45 or so) with fairly unique descriptors. Having a specific event type to each error message also allows me to toss up a dashboard with the daily average over the last month for each event type, compared with the last 24 hours. That way I can catch changes in known errors. Food for thought &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2011 08:17:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Setting-alerts-on-exceptions/m-p/41676#M518</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-02-10T08:17:46Z</dc:date>
    </item>
  </channel>
</rss>

