Getting Data In

maxDist value varies (in forwarders)

rotten
Communicator

I've noticed that the maxDist value in the props.conf on various lightweight forwarders varies. I've never explicitly set the value. I'm wondering how and why it is getting set from the default. It seems almost random depending on the forwarder I look at. (from 500 to 888)

Is it something I should manually adjust?

Tags (1)

Stephen_Sorkin
Splunk Employee
Splunk Employee

This is a parameter set by automatic sourcetype learning. There is no value in you setting this on your own.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...