Getting Data In

Communication between forwarder and indexer

clyde772
Communicator

Hey Splunkers!

I always thought or heard that data that gets input to forwarder gets "cooked" meaning compressed before it gets sent over to Indexer, but when we actually done a TCP DUMP to see the data, we ware able to see it as ASCII.

What is true? Based on the TCPDUMP capture we were able to see the ASCII data, so that proves that the data isn't being compressed / "Cooked".

Anybody know the answer to this?

Tags (1)
0 Karma

sdaniels
Splunk Employee
Splunk Employee

If you look at inputs.conf you'll have to configure it. The default setting is false for compression.

compressed = [true|false]
* Specifies whether receiving compressed data.
* If set to true, the forwarder port(s) should also have compression turned on; otherwise, the receiver will
reject the connection.
* Defaults to false.

0 Karma
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!

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...