<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source= in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/AggregatorMiningProcessor-Breaking-event-because-limit-of-256/m-p/459968#M79407</link>
    <description>&lt;P&gt;props.cong MAX_EVENTS&lt;BR /&gt;
see this answer:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/141721/error-in-splunkd-log-breaking-event-because-limit-of-256-has-been-exceeded.html"&gt;https://answers.splunk.com/answers/141721/error-in-splunkd-log-breaking-event-because-limit-of-256-has-been-exceeded.html&lt;/A&gt;&lt;BR /&gt;
make sure to have the props.conf on your first full splunk instance Heavy Forwarder OR Indexer&lt;/P&gt;

&lt;P&gt;hope it helps&lt;/P&gt;</description>
    <pubDate>Thu, 26 Jul 2018 14:48:40 GMT</pubDate>
    <dc:creator>adonio</dc:creator>
    <dc:date>2018-07-26T14:48:40Z</dc:date>
    <item>
      <title>AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source=</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AggregatorMiningProcessor-Breaking-event-because-limit-of-256/m-p/459967#M79406</link>
      <description>&lt;P&gt;we are getting the below errors from splunkd.log. the issue is we weren't able to search the logs from splunk console:&lt;/P&gt;

&lt;P&gt;have  tried editing TRUNCATE &amp;amp; DATETIME_CONFIG, this didn't help. can any one please help&lt;/P&gt;

&lt;P&gt;07-26-2018 15:41:55.605 +0200 WARN  AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source=&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jul 2018 13:53:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AggregatorMiningProcessor-Breaking-event-because-limit-of-256/m-p/459967#M79406</guid>
      <dc:creator>sandeepkalra</dc:creator>
      <dc:date>2018-07-26T13:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: AggregatorMiningProcessor - Breaking event because limit of 256 has been exceeded - data_source=</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/AggregatorMiningProcessor-Breaking-event-because-limit-of-256/m-p/459968#M79407</link>
      <description>&lt;P&gt;props.cong MAX_EVENTS&lt;BR /&gt;
see this answer:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/141721/error-in-splunkd-log-breaking-event-because-limit-of-256-has-been-exceeded.html"&gt;https://answers.splunk.com/answers/141721/error-in-splunkd-log-breaking-event-because-limit-of-256-has-been-exceeded.html&lt;/A&gt;&lt;BR /&gt;
make sure to have the props.conf on your first full splunk instance Heavy Forwarder OR Indexer&lt;/P&gt;

&lt;P&gt;hope it helps&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jul 2018 14:48:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/AggregatorMiningProcessor-Breaking-event-because-limit-of-256/m-p/459968#M79407</guid>
      <dc:creator>adonio</dc:creator>
      <dc:date>2018-07-26T14:48:40Z</dc:date>
    </item>
  </channel>
</rss>

