Configure the Monitoring Console in distributed mode
The following steps show you how to configure the monitoring console in distributed mode manually. Optionally, you can enable the monitoring console to configure distributed mode automatically. See Enable automatic distributed mode configuration.
To configure the monitoring console in distributed mode:
- Log into the instance on which you want to configure the monitoring console. The instance by default is in standalone mode, unconfigured.
- In Splunk Web, select Monitoring Console > Settings > General Setup.
- Click Distributed mode.
- Confirm the following:
- The columns labeled instance and machine are populated correctly and show unique values within each column.
- The server roles are correct. For example, a search head that is also a license manager must have both server roles listed. If not, click Edit > Edit Server Roles and select the correct server roles for the instance.
- If you are using indexer clustering, make sure the cluster manager instance is set to the cluster manager server role. If not, click Edit > Edit Server Roles and select the correct server role.
- If you are hosting the monitoring console on an instance other than the cluster manager, you must add the cluster manager instance as a search peer and configure the monitoring console instance as a search head in that cluster. See Enable a search head in Managing Indexers and Clusters of Indexers.
- To monitor a multisite indexer cluster, you must configure the monitoring console as a multisite search head. See Configure the search heads in Managing Indexers and Clusters of Indexers.
- Make sure anything marked as an indexer is actually an indexer.
- (Optional) Set custom groups. Custom groups are tags that map directly to distributed search groups. You might find groups useful, for example, if you have multisite indexer clustering in which each group can consist of the indexers in one location, or if you have an indexer cluster plus standalone peers. Custom groups are allowed to overlap. For example, one indexer can belong to multiple groups. See Create distributed search groups in the Distributed Search manual.
- Click Apply Changes.
If you add another node to your deployment later, click Settings > General Setup and check that these items are accurate.
Enable automatic distributed mode configuration
You can optionally enable automatic distributed mode configuration for the monitoring console. When enabled, the monitoring console automatically identifies existing search peers and configures itself in distributed mode. You must have search peers already added to the monitoring console before you can use automatic distributed mode configuration. For more information, see Add Splunk Enterprise instances to the monitoring console.
To enable automatic distributed mode configuration:
- Edit the
- Under the
mc_auto_configto enable, as shown:
[settings] mc_auto_config = enabled
- If you want to implement automatic distributed mode configuration immediately, restart Splunk. Otherwise, changes are implemented automatically every hour with no restart required.
Reset server roles after restart
After you configure the monitoring console in distributed mode, a restart of the instance hosting the monitoring console can cause any changes to server role settings on the instances you are monitoring to be lost.
To properly reset server roles after restart of the distributed monitoring console:
- Click Settings > General Setup > Reset All Settings > Refresh.
This restores the monitoring console to its original default configuration.
- Click Distributed.
- For the remote instances whose server roles you want to change, click Edit.
- Select or remove the specific server roles. Click Save.
- Click Apply Changes.
To configure the monitoring console for forwarders, see Configure forwarder monitoring for the Monitoring Console.
Configure Monitoring Console in standalone mode
Configure forwarder monitoring for the Monitoring Console
This documentation applies to the following versions of Splunk® Enterprise: 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.1.0, 9.1.1, 9.1.2