<?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: Search to match high temp events, but ignore specific events on host that trigger within 25 seconds of each other in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/659036#M227607</link>
    <description>&lt;P&gt;Yes, this is definitely useful, thank you for the help!&lt;/P&gt;</description>
    <pubDate>Fri, 29 Sep 2023 05:34:23 GMT</pubDate>
    <dc:creator>rprior</dc:creator>
    <dc:date>2023-09-29T05:34:23Z</dc:date>
    <item>
      <title>Search to match high temp events, but ignore specific events on host that trigger within 25 seconds of each other</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/658816#M227541</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;We have a Splunk alert that searches for high temperature events on Juniper routers, it's a very straight forward search:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=main CHASSISD_FRU_HIGH_TEMP_CONDITION OR CHASSISD_OVER_TEMP_SHUTDOWN_TIME OR CHASSISD_OVER_TEMP_CONDITION OR CHASSISD_TEMP_HOT_NOTICE OR CHASSISD_FPC_OPTICS_HOT_NOTICE OR CHASSISD_HIGH_TEMP_CONDITION OR (CHASSISD "Temperature back to normal") NOT UI_CMDLINE_READ_LINE&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd like this Splunk alert to &lt;STRONG&gt;ignore&lt;/STRONG&gt; &lt;U&gt;temperature alarm events on the host &lt;STRONG&gt;router4-utah&lt;/STRONG&gt;&lt;/U&gt;&amp;nbsp;when&amp;nbsp;&lt;STRONG&gt;FPC 11&lt;/STRONG&gt; =&amp;nbsp;&lt;FONT face="courier new,courier"&gt;FPC: MPC5E 3D 24XGE+6XLGE @ 11/*/*&lt;/FONT&gt;&amp;nbsp;is running hot, the events always come in the following order within 25 seconds of each other:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The alarm trigger events:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Sep 27 05:26:00  re0.router4-utah chassisd[7726]: CHASSISD_BLOWERS_SPEED_FULL: Fans and impellers being set to full speed [system warm]
Sep 27 05:26:00  re0.router4-utah alarmd[7895]: Alarm set: Temp sensor color=YELLOW, class=CHASSIS, reason=Temperature Warm
Sep 27 05:26:00  re0.router4-utah craftd[7730]:  Minor alarm set, Temperature Warm
Sep 27 05:26:00  re0.router4-utah chassisd[7726]: CHASSISD_HIGH_TEMP_CONDITION: Chassis temperature over 60 degrees C (but no fan/impeller failure detected)
Sep 27 05:26:02  re0.router4-utah chassisd[7726]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Over Temperature! (jnxContentsContainerIndex 7, jnxContentsL1Index 12, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr FPC: MPC5E 3D 24XGE+6XLGE @ 11/*/*, jnxOperatingTemp 91)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The alarm clear events:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Sep 27 05:26:21  re0.router4-utah alarmd[7895]: Alarm cleared: Temp sensor color=YELLOW, class=CHASSIS, reason=Temperature Warm
Sep 27 05:26:21  re0.router4-utah craftd[7730]: Minor alarm cleared, Temperature Warm&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The goal is to keep the normal temperature alert running as it always has, but somehow ignore&amp;nbsp;&lt;U&gt;the host &lt;STRONG&gt;router4-utah&lt;/STRONG&gt;&lt;/U&gt;&amp;nbsp;when it triggers and clears temperature alarms on FPC11. I think the easiest way to say this is any temp alarm that &lt;EM&gt;triggers&lt;/EM&gt; and &lt;EM&gt;clears&lt;/EM&gt; on&amp;nbsp;&lt;U&gt;&lt;STRONG&gt;router4-utah&lt;/STRONG&gt;&lt;/U&gt; that is surrounded &lt;U&gt;within 25 seconds&lt;/U&gt; of this line:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Sep 27 05:26:02 re0.router4-utah chassisd[7726]: CHASSISD_SNMP_TRAP6: SNMP trap generated: Over Temperature! (jnxContentsContainerIndex 7, jnxContentsL1Index 12, jnxContentsL2Index 0, jnxContentsL3Index 0, jnxContentsDescr FPC: MPC5E 3D 24XGE+6XLGE @ 11/*/*, jnxOperatingTemp 91)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any assistance one can provide is much appreciated! Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 27 Sep 2023 06:50:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/658816#M227541</guid>
      <dc:creator>rprior</dc:creator>
      <dc:date>2023-09-27T06:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: Search to match high temp events, but ignore specific events on host that trigger within 25 seconds of each other</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/659029#M227604</link>
      <description>&lt;P&gt;Looks like a good use case for &lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/SearchReference/Transaction" target="_blank" rel="noopener"&gt;transaction&lt;/A&gt;. (You must have search window &amp;gt; 25s in this case.)&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=main (host=re0.router4-utah "Alarm cleared: Temp sensor" color=YELLOW, class=CHASSIS, "reason=Temperature Warm") OR CHASSISD_FRU_HIGH_TEMP_CONDITION OR CHASSISD_OVER_TEMP_SHUTDOWN_TIME OR CHASSISD_OVER_TEMP_CONDITION OR CHASSISD_TEMP_HOT_NOTICE OR CHASSISD_FPC_OPTICS_HOT_NOTICE OR CHASSISD_HIGH_TEMP_CONDITION OR (CHASSISD "Temperature back to normal") NOT UI_CMDLINE_READ_LINE
| transaction host maxspan=25s startswith="CHASSISD_HIGH_TEMP_CONDITION" endswith="Alarm cleared: Temp sensor"
| where closed_txn == 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Sep 2023 03:28:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/659029#M227604</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2023-09-29T03:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: Search to match high temp events, but ignore specific events on host that trigger within 25 seconds of each other</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/659036#M227607</link>
      <description>&lt;P&gt;Yes, this is definitely useful, thank you for the help!&lt;/P&gt;</description>
      <pubDate>Fri, 29 Sep 2023 05:34:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Search-to-match-high-temp-events-but-ignore-specific-events-on/m-p/659036#M227607</guid>
      <dc:creator>rprior</dc:creator>
      <dc:date>2023-09-29T05:34:23Z</dc:date>
    </item>
  </channel>
</rss>

