When viewing the status of instances on the monitoring console, a member that has been removed is still listed.
In this example scenario, an indexer which was moved to a different network and its IP address was changed, but is still listed with its old IP. As a result, the Monitoring Console reports it as "unreachable", and under its Indexer Clustering: Status page, says "Replication Factor is Not Met", even though the Cluster Manager's Console (Settings > Indexer Clustering) says the instance is up and Search Factor and Replication Factor are met.
This article may be applicable for any instance which has been removed from your deployment yet still appears the Monitoring Console.
An indexer showing on the Monitoring Console as "unreachable" and Replication factor not being met can be caused by many things, such as OS misconfigurations like network, routing, or DNS, system-level performance problems at the OS level e.g. virtualization or poor performance of the network stack, misconfiguration of Splunk, or the Splunk performance itself.
For this example, its clear an indexer appears on the Cluster Manager's Console through Settings > Indexer Clustering, it shows as "Up" and the Cluster Manager shows search factor and replication factor are met, assuming there are no other issues currently occurring in the environment.
For search heads or other instances that have been removed from the deployment or their information has changed (ip address or host name), you could encounter similar issues where the instance appears correctly everywhere except within the Monitoring Console.
This type of issue can occur for any instance which is monitored by the Splunk Monitoring Console. The Monitoring Console may be on its own Splunk instance or your deployment may have it co-located with other management nodes such as the License Manager, Cluster Manager or Deployment Server. A Monitoring Console on its own instance might also be configured to monitor more than one Splunk deployment.
In these cases, if instances in the deployment have been removed or their information changed but they are not showing correctly on the Monitoring Console, it is very simple to confirm whether the Monitoring Console contains old or "orphaned" records. Two ways to check for this include:
Note: in the case of indexers, this article assumes a clustered indexer appears correctly as "Up" on the Cluster Manager's Indexer Clustering page, and no other issues are reported from the Cluster Manager point of view.
First, on the Monitoring Console's GUI:
If this does not solve the issue: from the Monitoring Console's CLI:
$SPLUNK_HOME/etc/apps/splunk_monitoring_console/local/splunk_monitoring_console_assets.confUpdate the affected instance (in this example, its IP Address)$SPLUNK_HOME etc/apps/splunk_monitoring_console/lookups/assets.csv, and check for information on the affected instance(s). Update if needed (as applicable for your situation)Splunk Documentation
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |