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!

Cisco Data Fabric from Architecture to Investigation, Better SOC Visibility, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

The Trust Gap: Why a Data Foundation is Fundamental to an Agentic Enterprise

The Trust Gap: Why a data foundation is fundamental to an  Agentic Enterprise.   Agentic AI is transforming ...

Data Management Digest – September 2026

    Welcome to the September 2026 edition of Data Management Digest! September brought a fresh wave of ...