Getting Data In

MAX_EVENTS in props.conf not working

fcologno
New Member

Hi everyone,

We have the following Splunk configuration:

  • Splunk Cloud instance (managed)
  • Universal Forwarder
  • Monitoring log

We need to index event logs with more than 256 lines.
props.conf (located at: SplunkUniversalForwarder\etc\system\local) has the following configuration:

[esb]
disabled = false
TRUNCATE = 0
LINE_BREAKER = ^.{4}-.{2}-.{2}\s.*
SHOULD_LINEMERGE = true
MAX_EVENTS = 100000

At search time, events appear truncated at max of 257 lines so, I suppose, that MAX_EVENTS props.conf isn't working.

How can i solve this issue?

Thanks

0 Karma

woodcock
Esteemed Legend

These are Indexer configurations, not UF configurations. They need to be deployed to your Indexer tier inside of Splunk Cloud. You will probably need to open a support ticket to get that done. They are in the wrong place.

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!

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