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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...