Use forwarders to get data in
Forwarders are Splunk Enterprise instances that consume data and send it to Splunk Enterprise indexers for processing. They 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 install a Splunk Enterprise indexer and then set up forwarders on the Apache hosts. The forwarders take the Apache data and send it on to the indexer, which then consolidates, stores, and makes it 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 a central Splunk Enterprise instance, 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 consume data like any other Splunk Enterprise instance. They can handle exactly the same types of data as an indexer. The difference is that forwarders usually do not index the data themselves. Instead, they get the data and send it on to an indexer, which does the indexing and searching. A single indexer can process data that comes from many forwarders. For detailed information on forwarders, see the Fowarding Data or Universal Forwarder manuals.
In most Splunk Enterprise deployments, forwarders serve as the primary consumers of data. It is only in single-machine deployments that the indexer might also be the main data consumer. In a large Splunk Enterprise deployment, you might have hundreds or even thousands of forwarders that consume data and forward it on to a group of indexers for consolidation.
How to configure forwarder inputs
As lightweight instances of Splunk Enterprise, forwarders have limited capabilities by design. For example, most forwarders do not include Splunk Web, which means no web interface is available to set up data inputs. 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 on a full Splunk Enteprise test instance to configure the inputs and then distribute the resulting
inputs.conffile to the forwarder.
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