<?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: Query for Splunkd Status in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295741#M164850</link>
    <description>&lt;P&gt;@wvalente, there could be several ways to identify this. &lt;/P&gt;

&lt;P&gt;1) By &lt;CODE&gt;_internal&lt;/CODE&gt; index has already been called out by Giuseppe. For remaining like:&lt;BR /&gt;
2) &lt;CODE&gt;metadata&lt;/CODE&gt; command&lt;BR /&gt;
3) REST api with &lt;CODE&gt;lastPhoneHomeTime&lt;/CODE&gt;  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| rest /services/deployment/server/clients
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTdeploy#deployment.2Fserver.2Fclients"&gt;https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTdeploy#deployment.2Fserver.2Fclients&lt;/A&gt;)&lt;BR /&gt;
4) &lt;CODE&gt;Distributed Monitoring Console&lt;/CODE&gt; to monitor deployment status, which uses above REST API.&lt;/P&gt;

&lt;P&gt;Refer to answer by @DalJeanis which compiles all these and more &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/525926/how-do-we-determine-whether-a-forwarder-phoned-hom.html"&gt;https://answers.splunk.com/answers/525926/how-do-we-determine-whether-a-forwarder-phoned-hom.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 25 Nov 2017 16:51:53 GMT</pubDate>
    <dc:creator>niketn</dc:creator>
    <dc:date>2017-11-25T16:51:53Z</dc:date>
    <item>
      <title>Query for Splunkd Status</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295739#M164848</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;

&lt;P&gt;There's any query in the splunk web that I'm able to see if the splunkd is not running in a forwarder?&lt;/P&gt;

&lt;P&gt;Tks.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 13:34:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295739#M164848</guid>
      <dc:creator>wvalente</dc:creator>
      <dc:date>2017-11-24T13:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: Query for Splunkd Status</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295740#M164849</link>
      <description>&lt;P&gt;Hi wvalente,&lt;BR /&gt;
you can check if your forwarders are sending logs to Splunk, reasons for this situations could be many (splunkd not running, network problems, host down, etc...) but anyway I think that you should check if a forwarder is sending logs and not if slunkd is running, anyway if there are other problems you cannot receive logs from the forwarder!&lt;/P&gt;

&lt;P&gt;So, to check if a forwarder is sending logs you can search on _internal&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal host=your_host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;if you don't receive logs  there's a problem.&lt;/P&gt;

&lt;P&gt;You can create an alert using a lookup (calling e.g. perimeter.csv) containing all the hosts to monitor and running e.g. every 5 minutes the following search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_internal
| eval host=upper(host)
| stats count by host
| append [ 
     | inputlookup perimeter.csv
     | eval host=upper(host), count=0
     | fields host count
     ]
| stats sum(count) AS Total by host
| where Total=0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In this way, hosts where Total=0 are missing and hosts where Total&amp;gt;0 are sending logs.&lt;BR /&gt;
You can also show host status in a dashboard (also in graphic mode).&lt;/P&gt;

&lt;P&gt;Bye.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 14:47:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295740#M164849</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2017-11-24T14:47:21Z</dc:date>
    </item>
    <item>
      <title>Re: Query for Splunkd Status</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295741#M164850</link>
      <description>&lt;P&gt;@wvalente, there could be several ways to identify this. &lt;/P&gt;

&lt;P&gt;1) By &lt;CODE&gt;_internal&lt;/CODE&gt; index has already been called out by Giuseppe. For remaining like:&lt;BR /&gt;
2) &lt;CODE&gt;metadata&lt;/CODE&gt; command&lt;BR /&gt;
3) REST api with &lt;CODE&gt;lastPhoneHomeTime&lt;/CODE&gt;  &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| rest /services/deployment/server/clients
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(&lt;A href="https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTdeploy#deployment.2Fserver.2Fclients"&gt;https://docs.splunk.com/Documentation/Splunk/latest/RESTREF/RESTdeploy#deployment.2Fserver.2Fclients&lt;/A&gt;)&lt;BR /&gt;
4) &lt;CODE&gt;Distributed Monitoring Console&lt;/CODE&gt; to monitor deployment status, which uses above REST API.&lt;/P&gt;

&lt;P&gt;Refer to answer by @DalJeanis which compiles all these and more &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/525926/how-do-we-determine-whether-a-forwarder-phoned-hom.html"&gt;https://answers.splunk.com/answers/525926/how-do-we-determine-whether-a-forwarder-phoned-hom.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Nov 2017 16:51:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295741#M164850</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-11-25T16:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Query for Splunkd Status</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295742#M164851</link>
      <description>&lt;P&gt;I would use &lt;CODE&gt;tstats&lt;/CODE&gt; like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| tstats count max(_indextime) AS _time WHERE index="_*" AND host="YourHostHere"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;You can build an alert from there.&lt;/P&gt;</description>
      <pubDate>Sun, 26 Nov 2017 22:49:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295742#M164851</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-11-26T22:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: Query for Splunkd Status</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295743#M164852</link>
      <description>&lt;P&gt;Tks @woodcock, @cusello and @niketnilay&lt;/P&gt;

&lt;P&gt;I'll try this solutions.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 13:25:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Query-for-Splunkd-Status/m-p/295743#M164852</guid>
      <dc:creator>wvalente</dc:creator>
      <dc:date>2017-11-27T13:25:35Z</dc:date>
    </item>
  </channel>
</rss>

