<?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 Monitoring Forwarder Uptime in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Monitoring-Forwarder-Uptime/m-p/107580#M22615</link>
    <description>&lt;P&gt;I am looking to set up a monitoring tool (HP's Sitescope) to "watch" our forwarders to ensure they are up.  I am not sure specifically what I should watch in the forwarder (port, process, etc).  It seems the outgoing port changes after each restart, and I'm not sure that monitoring the Management Host Port (8089) would provide an accurate indication if the forwarder stopped working.&lt;/P&gt;

&lt;P&gt;Running Splunk 4.1.2..   I know 4.2 has forwarder monitoring built in, but I'm looking for an interim solution.&lt;/P&gt;

&lt;P&gt;Thank you,&lt;BR /&gt;
DevonK&lt;/P&gt;</description>
    <pubDate>Mon, 23 May 2011 18:22:20 GMT</pubDate>
    <dc:creator>devonk</dc:creator>
    <dc:date>2011-05-23T18:22:20Z</dc:date>
    <item>
      <title>Monitoring Forwarder Uptime</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitoring-Forwarder-Uptime/m-p/107580#M22615</link>
      <description>&lt;P&gt;I am looking to set up a monitoring tool (HP's Sitescope) to "watch" our forwarders to ensure they are up.  I am not sure specifically what I should watch in the forwarder (port, process, etc).  It seems the outgoing port changes after each restart, and I'm not sure that monitoring the Management Host Port (8089) would provide an accurate indication if the forwarder stopped working.&lt;/P&gt;

&lt;P&gt;Running Splunk 4.1.2..   I know 4.2 has forwarder monitoring built in, but I'm looking for an interim solution.&lt;/P&gt;

&lt;P&gt;Thank you,&lt;BR /&gt;
DevonK&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2011 18:22:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitoring-Forwarder-Uptime/m-p/107580#M22615</guid>
      <dc:creator>devonk</dc:creator>
      <dc:date>2011-05-23T18:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Forwarder Uptime</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Monitoring-Forwarder-Uptime/m-p/107581#M22616</link>
      <description>&lt;P&gt;i know you're thinking of using an external solution, but you could also set up an alert using this search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| metadata type=hosts | eval age = now() - lastTime | search age &amp;gt; 86400 | sort age d | convert ctime(lastTime) | fields age,host,lastTime
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;to show you forwarders that haven't been heard from in the last 24 hours. &lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2011 20:08:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Monitoring-Forwarder-Uptime/m-p/107581#M22616</guid>
      <dc:creator>piebob</dc:creator>
      <dc:date>2011-05-23T20:08:46Z</dc:date>
    </item>
  </channel>
</rss>

