<?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 do we analyze indexers/search head log? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261342#M21671</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;the splunkd.log on your indexers should be indexed automatically. You can find them by searching index=_internal. There you will find all internal splunk logdata.&lt;/P&gt;

&lt;P&gt;For getting the internal logs of your searchhead to the indexer tier look at this. This works similar for your master node.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata"&gt;http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;kind regards&lt;/P&gt;</description>
    <pubDate>Thu, 20 Oct 2016 19:09:22 GMT</pubDate>
    <dc:creator>TStrauch</dc:creator>
    <dc:date>2016-10-20T19:09:22Z</dc:date>
    <item>
      <title>How do we analyze indexers/search head log?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261341#M21670</link>
      <description>&lt;P&gt;I have a working environment using index discovery.&lt;/P&gt;

&lt;P&gt;While doing command 'tail -f' on idx01 (Indexer - master box), I notice the following logs.&lt;/P&gt;

&lt;H2&gt;idx01 (tail -f /opt/splunk/var/log/splunk/splunkd.log)&lt;/H2&gt;

&lt;P&gt;10-19-2016 20:59:27.187 +0000 WARN  DistributedPeerManager - Unable to distribute to peer named idx03 at uri &lt;A href="https://10.200.2.35:8089" target="_blank"&gt;https://10.200.2.35:8089&lt;/A&gt; because replication was unsuccessful. replicationStatus Failed failure info: failed_because_HTTP_REPLY_READ_FAILURE&lt;BR /&gt;
10-19-2016 20:59:27.187 +0000 WARN  DistributedPeerManager - Unable to distribute to peer named idx04 at uri &lt;A href="https://10.200.2.38:8089" target="_blank"&gt;https://10.200.2.38:8089&lt;/A&gt; because replication was unsuccessful. replicationStatus Failed failure info: failed_because_HTTP_CONNECTION_FAILURE&lt;BR /&gt;
10-19-2016 20:59:38.186 +0000 INFO  TcpOutputProc - Connected to idx=10.200.2.36:9997&lt;BR /&gt;
10-19-2016 20:59:46.316 +0000 WARN  DistributedBundleReplicationManager - Asynchronous bundle replication to 3 peer(s) succeeded; however it took too long (longer than 10 seconds): elapsed_ms=19129, tar_elapsed_ms=3726, bundle_file_size=75900KB, replication_id=1476910767, replication_reason="async replication allowed"&lt;/P&gt;

&lt;P&gt;I did search using this string  'Failed failure info' on splunk, but found nothing.&lt;/P&gt;

&lt;P&gt;I am not sure if logs on indexers  are parsed and indexed.&lt;BR /&gt;
What is the best practice to monitor/analyze logs on indexers/search head boxes?&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 11:28:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261341#M21670</guid>
      <dc:creator>makincerdas</dc:creator>
      <dc:date>2020-09-29T11:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: How do we analyze indexers/search head log?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261342#M21671</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;the splunkd.log on your indexers should be indexed automatically. You can find them by searching index=_internal. There you will find all internal splunk logdata.&lt;/P&gt;

&lt;P&gt;For getting the internal logs of your searchhead to the indexer tier look at this. This works similar for your master node.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata"&gt;http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;kind regards&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2016 19:09:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261342#M21671</guid>
      <dc:creator>TStrauch</dc:creator>
      <dc:date>2016-10-20T19:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: How do we analyze indexers/search head log?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261343#M21672</link>
      <description>&lt;P&gt;I did not use 'index=_internal' on earlier attempt.&lt;BR /&gt;
It works by entering the following search, using 'index=_internal'&lt;/P&gt;

&lt;P&gt;index="_internal" Failed failure info source="/opt/splunk/var/log/splunk/splunkd.log"&lt;/P&gt;

&lt;P&gt;Thank you &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/160192"&gt;@TStrauch&lt;/a&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 11:31:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-we-analyze-indexers-search-head-log/m-p/261343#M21672</guid>
      <dc:creator>makincerdas</dc:creator>
      <dc:date>2020-09-29T11:31:44Z</dc:date>
    </item>
  </channel>
</rss>

