<?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: Monitor search peers in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25089#M4689</link>
    <description>&lt;P&gt;Here are 2 methods to detect if search peer is down, or hasn't responded to a search.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Schedule a search and count the number of peer responding&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Pick a search that should always return results, and count the number of search-peers, &lt;BR /&gt;
Then setup an email alert based on the number of search-peers (including the search head)&lt;/P&gt;

&lt;P&gt;Schedule the search every 5 minutes over last 2hours, and use the alert condition :&lt;BR /&gt;
if number of events is less than X&lt;BR /&gt;
&lt;PRE&gt;index=_internal splunk_server=* | stats count by splunk_server&lt;/PRE&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Schedule a search looking in the logs for errors &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;This is to detect an failure in a search afterward. &lt;BR /&gt;
By example schedule this search to run every 5 minutes over the last 5 minutes.&lt;BR /&gt;
&lt;PRE&gt;index=_internal source=*splunkd.log "Unable to connect to peer"&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;One remark, a search peer may not respond because of long searches that are hitting the timeout settings, you can increase them if its the case.&lt;BR /&gt;
see : connectionTimeout, sendTimeout, receiveTimeout in distsearch.conf &lt;BR /&gt;
&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Distsearchconf" target="_blank"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Distsearchconf&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 09:40:29 GMT</pubDate>
    <dc:creator>yannK</dc:creator>
    <dc:date>2020-09-28T09:40:29Z</dc:date>
    <item>
      <title>Monitor search peers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25088#M4688</link>
      <description>&lt;P&gt;I have 2 servers, Splunk1 and Splunk2, setup as search peers.  How can I monitor when one of the servers goes down or stops responding using Splunk?  I have received messages like the following:&lt;/P&gt;

&lt;P&gt;-- Search generated the following messages -- &lt;BR /&gt;
Message Level: ERROR &lt;BR /&gt;
1. Reading error while waiting for peer SPLUNK2. Search results might be incomplete! &lt;/P&gt;

&lt;P&gt;I would like to be alerted when something like this happens.  Does anyone have any ideas?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jun 2011 17:40:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25088#M4688</guid>
      <dc:creator>jec013</dc:creator>
      <dc:date>2011-06-08T17:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor search peers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25089#M4689</link>
      <description>&lt;P&gt;Here are 2 methods to detect if search peer is down, or hasn't responded to a search.&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Schedule a search and count the number of peer responding&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;Pick a search that should always return results, and count the number of search-peers, &lt;BR /&gt;
Then setup an email alert based on the number of search-peers (including the search head)&lt;/P&gt;

&lt;P&gt;Schedule the search every 5 minutes over last 2hours, and use the alert condition :&lt;BR /&gt;
if number of events is less than X&lt;BR /&gt;
&lt;PRE&gt;index=_internal splunk_server=* | stats count by splunk_server&lt;/PRE&gt;&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;Schedule a search looking in the logs for errors &lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;This is to detect an failure in a search afterward. &lt;BR /&gt;
By example schedule this search to run every 5 minutes over the last 5 minutes.&lt;BR /&gt;
&lt;PRE&gt;index=_internal source=*splunkd.log "Unable to connect to peer"&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;One remark, a search peer may not respond because of long searches that are hitting the timeout settings, you can increase them if its the case.&lt;BR /&gt;
see : connectionTimeout, sendTimeout, receiveTimeout in distsearch.conf &lt;BR /&gt;
&lt;A href="http://www.splunk.com/base/Documentation/latest/Admin/Distsearchconf" target="_blank"&gt;http://www.splunk.com/base/Documentation/latest/Admin/Distsearchconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 09:40:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25089#M4689</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2020-09-28T09:40:29Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor search peers</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25090#M4690</link>
      <description>&lt;P&gt;Back in Version 3, on the main search screen, you would see a not "x of y" servers .  For example, "5 of 5" Servers. If one was not responding, you could pull down a tab and immediately see which one.&lt;/P&gt;

&lt;P&gt;This was a good idea, and meant your users would immediately see any issue.  I would like to suggest seeing it come back.  &lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2014 19:41:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Monitor-search-peers/m-p/25090#M4690</guid>
      <dc:creator>JimDeich</dc:creator>
      <dc:date>2014-05-09T19:41:23Z</dc:date>
    </item>
  </channel>
</rss>

