<?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: group fields in search command in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/group-fields-in-search-command/m-p/103804#M26839</link>
    <description>&lt;P&gt;In general you'd want some overlap in your search.  So, if your search runs at 0:00, 3:00, and 6:00, you wouldn't want the search to only look back 3 hours.  You'd want to look back maybe 3 hours 15 minutes.  &lt;/P&gt;

&lt;P&gt;However, that won't completely solve your problem because the outage could be days long.  Maybe you could add something like this if there's no up event?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | eval do_alert=if(now() - _time &amp;gt;= 180, "True", "False")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And then on the schedule set the alert to a custom condition of: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;search do_alert=True
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Mon, 13 Dec 2010 11:31:09 GMT</pubDate>
    <dc:creator>mw</dc:creator>
    <dc:date>2010-12-13T11:31:09Z</dc:date>
    <item>
      <title>group fields in search command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/group-fields-in-search-command/m-p/103803#M26838</link>
      <description>&lt;P&gt;i would like to send an alert when newwork interface is down more than 3 min. That is to say i wanna group the field named "Status" together which value is either up or down, and the time difference is within 3 min. Now if i use "%LINK-3-UPDOWN"... | transaction host, interface | where eventcont%2!=0 per 3 min. but it have problems when e.g. down event is at 2:50 and up is at 3:10 (scheduled search is at 0:00,3:00,6:00...) even covering the search time range still exists this problem. any other best way to do this? thanks and regards,&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2010 10:40:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/group-fields-in-search-command/m-p/103803#M26838</guid>
      <dc:creator>hjwang</dc:creator>
      <dc:date>2010-12-13T10:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: group fields in search command</title>
      <link>https://community.splunk.com/t5/Splunk-Search/group-fields-in-search-command/m-p/103804#M26839</link>
      <description>&lt;P&gt;In general you'd want some overlap in your search.  So, if your search runs at 0:00, 3:00, and 6:00, you wouldn't want the search to only look back 3 hours.  You'd want to look back maybe 3 hours 15 minutes.  &lt;/P&gt;

&lt;P&gt;However, that won't completely solve your problem because the outage could be days long.  Maybe you could add something like this if there's no up event?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;... | eval do_alert=if(now() - _time &amp;gt;= 180, "True", "False")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And then on the schedule set the alert to a custom condition of: &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;search do_alert=True
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 13 Dec 2010 11:31:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/group-fields-in-search-command/m-p/103804#M26839</guid>
      <dc:creator>mw</dc:creator>
      <dc:date>2010-12-13T11:31:09Z</dc:date>
    </item>
  </channel>
</rss>

