<?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 monitor deployed universal forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186172#M37306</link>
    <description>&lt;P&gt;Hi joshk2005,&lt;/P&gt;

&lt;P&gt;check out the deployment monitor app &lt;A href="https://apps.splunk.com/app/1294/"&gt;https://apps.splunk.com/app/1294/&lt;/A&gt; which includes such searches like missing forwarder and other stuff which can be useful. Also check out the S.o.S app &lt;A href="https://apps.splunk.com/app/748/"&gt;https://apps.splunk.com/app/748/&lt;/A&gt; or if you're using Splunk 6.2 have a look at the &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/ConfiguretheMonitoringConsole"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/ConfiguretheMonitoringConsole&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2015 13:45:16 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-01-19T13:45:16Z</dc:date>
    <item>
      <title>How to monitor deployed universal forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186171#M37305</link>
      <description>&lt;P&gt;We sporadically have had issues where the forwarder service stops working due to the need to clear locks on the client.  Is there a good search string that we could use to alert off of when specific forwarders stop working? We are specifically looking to ensure that our domain controllers do not stop forwarding data (for long) due to the forwarder service not running.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 13:33:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186171#M37305</guid>
      <dc:creator>joshk2005</dc:creator>
      <dc:date>2015-01-19T13:33:49Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor deployed universal forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186172#M37306</link>
      <description>&lt;P&gt;Hi joshk2005,&lt;/P&gt;

&lt;P&gt;check out the deployment monitor app &lt;A href="https://apps.splunk.com/app/1294/"&gt;https://apps.splunk.com/app/1294/&lt;/A&gt; which includes such searches like missing forwarder and other stuff which can be useful. Also check out the S.o.S app &lt;A href="https://apps.splunk.com/app/748/"&gt;https://apps.splunk.com/app/748/&lt;/A&gt; or if you're using Splunk 6.2 have a look at the &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/ConfiguretheMonitoringConsole"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/ConfiguretheMonitoringConsole&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 13:45:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186172#M37306</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-19T13:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to monitor deployed universal forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186173#M37307</link>
      <description>&lt;P&gt;Deployment monitor app is a great tool.   There is even built in options to create alerts easily - great time saver. &lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2015 18:45:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-monitor-deployed-universal-forwarders/m-p/186173#M37307</guid>
      <dc:creator>trsavela</dc:creator>
      <dc:date>2015-01-20T18:45:55Z</dc:date>
    </item>
  </channel>
</rss>

