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!

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 ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...