Use forwarders to get data in
Splunk forwarders consume data and send it to an indexer. Forwarders require minimal resources and have little impact on performance, so they can usually reside on the machines where the data originates.
For example, if you have a number of Apache Web servers that generate data that you want to search centrally, you can set up forwarders on the Apache hosts. The forwarders take the Apache data and send it to your Splunk deployment for indexing, which consolidates, stores, and makes the data available for searching. Because of their reduced resource footprint, forwarders have minimal performance impact on the Apache servers.
Similarly, you can install forwarders on your employees' Windows desktops. These can send logs and other data to your Splunk deployment, where you can view the data as a whole to track malware or other issues. The Splunk App for Windows Infrastructure relies on this kind of deployment.
What forwarders do
Forwarders get data from remote machines. They represent a more robust solution than raw network feeds, with their capabilities for the following actions:
- Tagging of metadata (source, sourcetype, and host)
- Configurable buffering
- Data compression
- SSL security
- Use of any available network ports
- Running scripted inputs locally
Forwarders usually do not index the data, but rather forward the data to a Splunk deployment that does the indexing and searching. A Splunk deployment can process data that comes from many forwarders. For detailed information on forwarders, see the Forwarding Data or Universal Forwarder manuals.
In most Splunk deployments, forwarders serve as the primary consumers of data. In a large Splunk deployment, you might have hundreds or even thousands of forwarders that consume data and forward for consolidation.
How to configure forwarder inputs
- Configure a Splunk Enterprise host to receive the data.
- Determine the kind of forwarder you want to put on the host with the data.
- You can use a heavy forwarder, which is a full Splunk Enterprise instance with forwarding turned on, or a universal forwarder, which its its own installation package.
- The type of forwarder you use depends on the performance requirements you have on the host and whether or not you need to transform the data in any way as it comes into Splunk.
- Download Splunk Enterprise or the universal forwarder for the platform and architecture of the host with the data.
- Install the forwarder onto the host.
- Enable forwarding on the host and specify a destination
- Configure inputs for the data that you want to collect from the host. You can use Splunk Web if the forwarder is a full Splunk Enterprise instance.
- Confirm that data from the forwarder arrives at the receiving indexer.
Here are the main ways that you can configure data inputs on a forwarder:
- Specify inputs during initial deployment.
- For Windows forwarders, specify common inputs during the installation process.
- For *nix forwarders, specify inputs directly after installation.
- Use the CLI.
- Edit inputs.conf.
- Install an app that contains the inputs you want.
- Use Splunk Web to configure the inputs and a deployment server to copy the resulting
inputs.conffile to forwarders.
Forwarder Topologies and Deployments
- For information on forwarders, including use cases, typical topologies, and configurations, see About forwarding and receiving in the Forwarding Data manual.
- For details on how to deploy the universal forwarder, including how to use the deployment server to simplify distribution of configuration files and apps to multiple forwarders, see Example forwarder deployment topologies in the Universal Forwarder manual.
Is my data local or remote?
Use apps to get data in
This documentation applies to the following versions of Splunk® Enterprise: 6.4.0, 6.4.1, 6.4.2, 6.4.3, 6.4.4, 6.4.5, 6.4.6, 6.4.7, 6.4.8, 6.4.9, 6.4.10, 6.4.11, 6.5.0, 6.5.1, 6.5.1612 (Splunk Cloud only), 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, 6.5.7, 6.5.8, 6.5.9, 6.5.10, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 6.6.7, 6.6.8, 6.6.9, 6.6.10, 6.6.11, 6.6.12, 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.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.2.0, 7.2.1, 7.2.2, 7.2.3