Splunk® Universal Forwarder

Forwarder Manual

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

The universal forwarder

About the universal forwarder

The universal forwarder collects data from a data source or another forwarder and sends it to a forwarder or a Splunk deployment. With a universal forwarder, you can send data to Splunk Enterprise, Splunk Light, or Splunk Cloud Platform. It also replaces the Splunk Enterprise light forwarder. The universal forwarder is available as a separate installation package.

The universal forwarder offers advantages over using a heavy or light forwarder. The most notable benefit is that it uses significantly fewer hardware resources than other Splunk software products. It can, for example, coexist on a host that runs a Splunk Enterprise instance. It also is more scalable than the other Splunk products, as you can install thousands of universal forwarders with little impact on network and host performance.

Another benefit is its availability for installation on many diverse computing platforms and architectures. You can install it on more platforms than you can Splunk Enterprise.

The universal forwarder includes only the essential components that it needs to forward data to other Splunk platform instances. While it does not have a Web interface, you can still configure, manage, and scale it by editing configuration files or by using the Forwarder Management or Monitoring Console interfaces in Splunk Web.

This manual discusses the universal forwarder

This manual discusses the universal forwarder and how to plan, download, install, and configure it. There are two other types of forwarders. To learn about heavy and light forwarders and how they forward data, see About forwarding and receiving data in the Forwarding Data Manual.

To achieve higher performance and a lighter resource footprint, the universal forwarder has a subset of the functionality provided by a full Splunk platform deployment, specifically:

  • Cannot search or index data.
  • Cannot send alerts.
  • Does not parse incoming data, except in certain cases, such as structured data or some forms of Windows data.
  • Cannot send data to syslog servers as it has no syslog pipeline.
  • Does not include a version of Python.

How the universal forwarder compares to the light forwarder

The light forwarder is a full Splunk Enterprise instance with certain features that have been disabled to achieve a smaller resource footprint. The universal forwarder differs from the light forwarder in the following ways:

  • It puts less load on the host CPU, uses less memory, and has a smaller disk space footprint.
  • It cannot be converted to function as a heavy forwarder or other Splunk Enterprise role.
  • It does not have Splunk Web, which means that you cannot perform any configuration with that user interface.

The light forwarder was deprecated in Splunk Enterprise version 6.0, which means that support for it can be removed in a future version of Splunk Enterprise. When you install the universal forwarder, you can migrate from an existing light forwarder that runs version 4.0 or later. See Migrate a Windows light forwarder or Migrate a *nix light forwarder for details.

Information on Windows third-party binaries that ship with the universal forwarder

For information on third-party Windows binaries provided with the Windows version of the universal forwarder, see Information on Windows third-party binaries distributed with Splunk Enterprise in the Splunk Enterprise Installation Manual.

For information about running the universal forwarder in Windows Safe Mode, see Splunk Enterprise Architecture and Processes also in the Installation Manual.

Last modified on 01 December, 2021
About forwarding and receiving data

This documentation applies to the following versions of Splunk® Universal Forwarder: 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.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.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, 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.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4

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