Splunk® Universal Forwarder

Forwarder Manual

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® Universal Forwarder. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Consolidate data from multiple hosts

One of the most common forwarding use cases is to consolidate data that originates across numerous machines. Forwarders located on the machines send the data to a central Splunk deployment. This diagram illustrates a common scenario, where universal forwarders residing on machines running diverse operating systems send data to a single Splunk instance, which indexes and provides search capabilities across all the data.

30 admin13 forwardreceive-dataforward 60.png

The diagram illustrates a small deployment. In practice, the number of universal forwarders in a data consolidation use case could number into the thousands.

1. Determine the data and machines you need to access.

2. Install a Splunk instance on a host.

This instance functions as the receiver. Data goes there to be indexed and searched.

3. Using the CLI, enter this command from $SPLUNK_HOME/bin/:

./splunk enable listen <port> -auth <username>:<password>
  • <port> is the network port you want the receiver to listen on.

4. Install universal forwarders on each machine that will generate data.

5. Configure inputs for each forwarder.

To learn what Splunk software can index and how to configure inputs, see What data can I index? in Getting Data In.

6. Configure each universal forwarder to send data to the receiver. For Windows forwarders, you can do this at installation time or through the CLI after installation. For *nix forwarders, you must do this through the CLI.

./splunk add forward-server <host>:<port> -auth <username>:<password>
  • <host>:<port> are the host and receiver port number of the receiver. For example, splunk_indexer.acme.com:9997.

Alternatively, if you have many forwarders, you can use an outputs.conf file to specify the receiver. For example:

[tcpout:my_indexers]
server= splunk_indexer.acme.com:9997

You can create this file once and distribute copies of it to each forwarder.

Last modified on 01 December, 2021
PREVIOUS
Install the universal forwarder software
  NEXT
Install a Windows universal forwarder from an installer

This documentation applies to the following versions of Splunk® Universal Forwarder: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters