Getting Data In

>256 lines events on universal forwarder

0range
Communicator

Hello.
How to load more than 256-line events when we use universal forwarders?

0 Karma

Ayn
Legend

This is not configured on the Universal Forwarders, but on the indexer. See the MAX_EVENTS directive in props.conf: http://docs.splunk.com/Documentation/Splunk/latest/admin/Propsconf

...so, to clarify, what you'd do is put something like this in:

[yoursourcetype]
MAX_EVENTS = 1000

kristian_kolb
Ultra Champion

This is a setting in props.conf on the indexer (or a Heavy Forwarder if you have that as a relay). By default Splunk will cut multline messages at 256 lines, and each line at 10000 bytes. This behaviour can be altered with the MAX_EVENTS and TRUNCATE parameters (respectively), e.g.

props.conf

[my_sourcetype]
SHOULD_LINEMERGE = true
BREAK_ONLY_BEFORE_DATE = true
MAX_EVENTS = 1024
TRUNCATE = 400

The above configuration will allow each message to contain up to 1024 lines, and each line can up to 400 bytes long.

See the documentation for props.conf for further details and other configuration options.

http://docs.splunk.com/Documentation/Splunk/latest/Admin/Propsconf

/K

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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...