<?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 Figuring out last host reported data based on lookup in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Figuring-out-last-host-reported-data-based-on-lookup/m-p/547651#M4964</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Looking for some advice on a popular topping of non reporting hosts.&amp;nbsp; Perhaps someone already came across something like this, or has a better way of doing it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have device pairs that report differently, and I am looking for a way to alert if a device stops reporting based on expected reporting&amp;nbsp; cadence for a particular device.&amp;nbsp; For example, have a CSV with device name/IP and a column for the expected reporting threshold that can be used to generate an alert if it is exceeded.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;FW1-primary, 2m&lt;BR /&gt;FW1-secondary, 4h&lt;/P&gt;&lt;P&gt;So the search can look at the second column, and if it's been more than 4 hours since FW1-secondary sent an event, an alert can be generated.&amp;nbsp; TIA!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Apr 2021 19:12:15 GMT</pubDate>
    <dc:creator>oleg106</dc:creator>
    <dc:date>2021-04-12T19:12:15Z</dc:date>
    <item>
      <title>Figuring out last host reported data based on lookup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Figuring-out-last-host-reported-data-based-on-lookup/m-p/547651#M4964</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Looking for some advice on a popular topping of non reporting hosts.&amp;nbsp; Perhaps someone already came across something like this, or has a better way of doing it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have device pairs that report differently, and I am looking for a way to alert if a device stops reporting based on expected reporting&amp;nbsp; cadence for a particular device.&amp;nbsp; For example, have a CSV with device name/IP and a column for the expected reporting threshold that can be used to generate an alert if it is exceeded.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;FW1-primary, 2m&lt;BR /&gt;FW1-secondary, 4h&lt;/P&gt;&lt;P&gt;So the search can look at the second column, and if it's been more than 4 hours since FW1-secondary sent an event, an alert can be generated.&amp;nbsp; TIA!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 19:12:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Figuring-out-last-host-reported-data-based-on-lookup/m-p/547651#M4964</guid>
      <dc:creator>oleg106</dc:creator>
      <dc:date>2021-04-12T19:12:15Z</dc:date>
    </item>
    <item>
      <title>Re: Figuring out last host reported data based on lookup</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Figuring-out-last-host-reported-data-based-on-lookup/m-p/547679#M4965</link>
      <description>&lt;P&gt;I would recommend doing it like this:&lt;/P&gt;&lt;P&gt;Lookup (demolookup):&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;host,seconds
somehostname,60&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Your alert search:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| metadata type=hosts | table host recentTime | lookup demolookup host | eval threshold=now()-seconds | where recentTime&amp;lt;threshold&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Apr 2021 22:06:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Figuring-out-last-host-reported-data-based-on-lookup/m-p/547679#M4965</guid>
      <dc:creator>ericjorgensenjr</dc:creator>
      <dc:date>2021-04-12T22:06:51Z</dc:date>
    </item>
  </channel>
</rss>

