Getting Data In

Impact of LineBreakingProcessor and AggregateMiningProcessor on indexing performance

swatishs
Explorer

When indexing a directory containing html files, log files, zipped log files and gzipped log files, I am getting many LineBreakingProcessor and AggregateMiningProcessor warnings. It is scattered with them.
LineBreakingProcessor: When a line exceepds a predefined lenght (default 10,000bytes)
AggregateMiningProcessor: When an event has more than 256 lines.

Can someone please elaborate more on the performance impact of these?

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!

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