Getting Data In

What are the main differences between the Universal forwarder and Heavy forwarder?

test_qweqwe
Builder

Can someone explain me in simply english the difference between there two forwards and where they are using?

0 Karma
1 Solution

somesoni2
Revered Legend

Generally description from below link would answer your question.
http://docs.splunk.com/Documentation/Splunk/6.6.3/Forwarding/Typesofforwarders

If not, a universal forwarder only does the collection and forwarding of data (collects data and sends to other Splunk instance where it'll be processed). It doesn't do data processing (event parsing, timestamp extractions , routing, masking etc) with exception of structured data types such as json, Whereas a heavy forwarder, as name suggests, does collection, processing and forwarding. A heavy forwarder can also do local indexing if configured to do so. Detailed differences can be found here: http://docs.splunk.com/Documentation/Splunk/6.6.3/Forwarding/Typesofforwarders#Forwarder_comparison

In most use-cases of data forwarding, you would use Universal forwarder and leave data processing to intermediate heavy forwarders/indexers. In cases where you want to do local indexing OR keep the data processing work away from indexers, you'd use heavy forwarders.

View solution in original post

somesoni2
Revered Legend

Generally description from below link would answer your question.
http://docs.splunk.com/Documentation/Splunk/6.6.3/Forwarding/Typesofforwarders

If not, a universal forwarder only does the collection and forwarding of data (collects data and sends to other Splunk instance where it'll be processed). It doesn't do data processing (event parsing, timestamp extractions , routing, masking etc) with exception of structured data types such as json, Whereas a heavy forwarder, as name suggests, does collection, processing and forwarding. A heavy forwarder can also do local indexing if configured to do so. Detailed differences can be found here: http://docs.splunk.com/Documentation/Splunk/6.6.3/Forwarding/Typesofforwarders#Forwarder_comparison

In most use-cases of data forwarding, you would use Universal forwarder and leave data processing to intermediate heavy forwarders/indexers. In cases where you want to do local indexing OR keep the data processing work away from indexers, you'd use heavy forwarders.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...