<?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: How to create an alert to trigger an email when a forwarder is stopped on a server? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271869#M52228</link>
    <description>&lt;P&gt;Hi athorat,&lt;/P&gt;

&lt;P&gt;forward the &lt;CODE&gt;_internal&lt;/CODE&gt; logs of the forwarder to the indexer and search like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal component=ShutdownHandler
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will list all &lt;CODE&gt;shutdown&lt;/CODE&gt; events.&lt;/P&gt;

&lt;P&gt;Basics about &lt;CODE&gt;_internal&lt;/CODE&gt; forwarding can be found here &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/DistSearch/Forwardsearchheaddata"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/DistSearch/Forwardsearchheaddata&lt;/A&gt; &lt;BR /&gt;
Yes, you can do the same on your forwarder.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Tue, 13 Oct 2015 23:56:41 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-10-13T23:56:41Z</dc:date>
    <item>
      <title>How to create an alert to trigger an email when a forwarder is stopped on a server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271868#M52227</link>
      <description>&lt;P&gt;We have a report which helps us to trigger an alert when the Indexer is down.&lt;BR /&gt;
Is there a way we can monitor if the forwarder is stopped on the server which can send an email alert?&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2015 23:32:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271868#M52227</guid>
      <dc:creator>athorat</dc:creator>
      <dc:date>2015-10-13T23:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alert to trigger an email when a forwarder is stopped on a server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271869#M52228</link>
      <description>&lt;P&gt;Hi athorat,&lt;/P&gt;

&lt;P&gt;forward the &lt;CODE&gt;_internal&lt;/CODE&gt; logs of the forwarder to the indexer and search like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal component=ShutdownHandler
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will list all &lt;CODE&gt;shutdown&lt;/CODE&gt; events.&lt;/P&gt;

&lt;P&gt;Basics about &lt;CODE&gt;_internal&lt;/CODE&gt; forwarding can be found here &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.3.0/DistSearch/Forwardsearchheaddata"&gt;http://docs.splunk.com/Documentation/Splunk/6.3.0/DistSearch/Forwardsearchheaddata&lt;/A&gt; &lt;BR /&gt;
Yes, you can do the same on your forwarder.&lt;/P&gt;

&lt;P&gt;Hope this helps ...&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Tue, 13 Oct 2015 23:56:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271869#M52228</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-10-13T23:56:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to create an alert to trigger an email when a forwarder is stopped on a server?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271870#M52229</link>
      <description>&lt;P&gt;Forwarders can be not forwarding for many reasons other than shutdown including a crash, which would not have a shutdown event or a network problem.  Try this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| metadata index=* type=hosts | eval latencySeconds=(recentTime-lastTime) | eval quietSeconds=(now()-recentTime) | fieldformat firstTime=strftime(firstTime, "%m/%d/%Y %H:%M:%S") | fieldformat lastTime=strftime(lastTime, "%m/%d/%Y %H:%M:%S") | eval indexTime=strftime(recentTime, "%m/%d/%Y %H:%M:%S")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The field &lt;CODE&gt;quietSeconds&lt;/CODE&gt; tells you how long it has been since that forwarder sent any data to any indexer.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2015 13:23:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-create-an-alert-to-trigger-an-email-when-a-forwarder-is/m-p/271870#M52229</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-10-14T13:23:48Z</dc:date>
    </item>
  </channel>
</rss>

