Getting Data In

event size limit

sbsbb
Builder

Is there any limit from the event-size ?

My events are truncated, one event is about 3Mo text. Is there a possibility to increase the event size in the config ?

Tags (3)
1 Solution

lguinn2
Legend

The default event size limit is 10000 characters. You can override this in props.conf as follows

[yoursourcetypehere]
TRUNCATE = 0
MAX_EVENTS = 10000

Setting TRUNCATE to zero means "no truncation". MAX_EVENTS actually sets "the maximum number of lines per event." MAX_EVENTS only applies to multi-line events, but the default is 256 lines. If you are dealing with multi-line events, you may want to set this to a much larger value.

You can put the props.conf file under an application, if it is application-specific, or under /etc/system/local

View solution in original post

lguinn2
Legend

The default event size limit is 10000 characters. You can override this in props.conf as follows

[yoursourcetypehere]
TRUNCATE = 0
MAX_EVENTS = 10000

Setting TRUNCATE to zero means "no truncation". MAX_EVENTS actually sets "the maximum number of lines per event." MAX_EVENTS only applies to multi-line events, but the default is 256 lines. If you are dealing with multi-line events, you may want to set this to a much larger value.

You can put the props.conf file under an application, if it is application-specific, or under /etc/system/local

mufthmu
Path Finder

hi @lguinn2 , I updated the props.conf in my indexer and forwarder but my data still get truncated to 100 KB.
According to this answer https://answers.splunk.com/answers/155691/why-are-larger-events-are-truncated-10000-bytes.html .. I also need to update the Heavy Forwarder's props.conf file. Do you know how to find out if my data flows thru the HWF before getting into the indexer?

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