Getting Data In

AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source=

sandeepkalra
New Member

we are getting the below errors from splunkd.log. the issue is we weren't able to search the logs from splunk console:

have tried editing TRUNCATE & DATETIME_CONFIG, this didn't help. can any one please help

07-26-2018 15:41:55.605 +0200 WARN AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source=

Tags (1)
0 Karma

adonio
Ultra Champion

props.cong MAX_EVENTS
see this answer:
https://answers.splunk.com/answers/141721/error-in-splunkd-log-breaking-event-because-limit-of-256-h...
make sure to have the props.conf on your first full splunk instance Heavy Forwarder OR Indexer

hope it helps

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!

A Four-Part Event Series: Full Stack Observability For the AI Era

As AI reshapes applications, infrastructure, and the way teams operate, the traditional boundaries of ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...