Best practice: Forward manager node data to the indexer layer
It is considered a best practice to forward all manager node internal data to the indexer (peer node) layer. This has several advantages:
- It accumulates all data in one place. This simplifies the process of managing your data: You only need to manage your indexes and data at one level, the indexer level.
- It enables diagnostics for the manager node if it goes down. The data leading up to the failure is accumulated on the indexers, where a search head can later access it.
The preferred approach is to forward the data directly to the indexers, without indexing separately on the manager node. You do this by configuring the manager node as a forwarder. These are the main steps:
1. Make sure that all necessary indexes exist on the indexers. This is normally the case, unless you have created custom indexes on the manager node. Since
_internal exist on indexers as well as the manager, you do not need to create separate versions of those indexes to hold the corresponding manager data.
2. Configure the manager node as a forwarder. Create an
outputs.conf file on the manager node that configures it for load-balanced forwarding across the set of peer nodes. You must also turn off indexing on the manager node, so that the manager does not both retain the data locally as well as forward it to the peers.
Here is an example
# Turn off indexing on the manager node [indexAndForward] index = false [tcpout] defaultGroup = my_peers_nodes forwardedindex.filter.disable = true indexAndForward = false [tcpout:my_peers_nodes] server=10.10.10.1:9997,10.10.10.2:9997,10.10.10.3:9997
This example assumes that each peer node's receiving port is set to 9997.
For details on configuring
outputs.conf, read "Configure forwarders with outputs.conf" in the Forwarding Data manual.
Enable the search head
Prepare the peers for index replication
This documentation applies to the following versions of Splunk® Enterprise: 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.2.0, 8.2.1, 8.2.2