<?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: Splunk shc member  abnormal in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748687#M10957</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/244721"&gt;@meng&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;You can also check the latest status of your search head cluster using REST endpoint as mentioned here -&amp;nbsp;&lt;A href="https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/9.4/cluster-endpoints/cluster-endpoint-descriptions#get-38" target="_blank"&gt;https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/9.4/cluster-endpoints/cluster-endpoint-descriptions#get-38&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It'll always fetch the latest information for your cluster. And as for getting inaccurate information from metadata, as&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;mentioned, open up a support case with Splunk.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Tejas.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jun 2025 10:06:12 GMT</pubDate>
    <dc:creator>tej57</dc:creator>
    <dc:date>2025-06-25T10:06:12Z</dc:date>
    <item>
      <title>Splunk shc member  abnormal</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748640#M10955</link>
      <description>I use metadata to monitor the activity status of member nodes in my cluster, but recently I discovered an exception. My SHC member 01 was found to be inactive, and the last time metadata was sent was a long time ago. However, when I checked my SHC cluster member status in the background, it was always in the up state, and the last time it was sent to the administrator was also recently. I restarted my member 1, but it seems that the latest time of member 1 cannot be seen in the metadata</description>
      <pubDate>Wed, 25 Jun 2025 02:21:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748640#M10955</guid>
      <dc:creator>meng</dc:creator>
      <dc:date>2025-06-25T02:21:58Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk shc member  abnormal</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748668#M10956</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/244721"&gt;@meng&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I never experienced this issue, opena a case to Splunk Support, for your case and also for the other Splunk Customer.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2025 08:30:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748668#M10956</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-06-25T08:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk shc member  abnormal</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748687#M10957</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/244721"&gt;@meng&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;You can also check the latest status of your search head cluster using REST endpoint as mentioned here -&amp;nbsp;&lt;A href="https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/9.4/cluster-endpoints/cluster-endpoint-descriptions#get-38" target="_blank"&gt;https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/9.4/cluster-endpoints/cluster-endpoint-descriptions#get-38&lt;/A&gt;&lt;/P&gt;&lt;P&gt;It'll always fetch the latest information for your cluster. And as for getting inaccurate information from metadata, as&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;mentioned, open up a support case with Splunk.&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Tejas.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2025 10:06:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-shc-member-abnormal/m-p/748687#M10957</guid>
      <dc:creator>tej57</dc:creator>
      <dc:date>2025-06-25T10:06:12Z</dc:date>
    </item>
  </channel>
</rss>

