<?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: Throttling repeated events in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349029#M11952</link>
    <description>&lt;P&gt;A good start would be the search that the "correlation rule" that is running and the schedule that's it is running on.&lt;/P&gt;</description>
    <pubDate>Sat, 17 Jun 2017 22:18:08 GMT</pubDate>
    <dc:creator>Richfez</dc:creator>
    <dc:date>2017-06-17T22:18:08Z</dc:date>
    <item>
      <title>Throttling repeated events</title>
      <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349026#M11949</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;  Even after configuring throttling the same correlation rule is gerating 1000's of incidents every 5 minutes, any idea how to resolve this    ?
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sat, 17 Jun 2017 15:35:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349026#M11949</guid>
      <dc:creator>arunthomas</dc:creator>
      <dc:date>2017-06-17T15:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: Throttling repeated events</title>
      <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349027#M11950</link>
      <description>&lt;P&gt;Please post the code, with confidential parts removed or masked, and then maybe we can suggest something.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Jun 2017 17:46:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349027#M11950</guid>
      <dc:creator>DalJeanis</dc:creator>
      <dc:date>2017-06-17T17:46:50Z</dc:date>
    </item>
    <item>
      <title>Re: Throttling repeated events</title>
      <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349028#M11951</link>
      <description>&lt;P&gt;What you mean by code ?&lt;/P&gt;</description>
      <pubDate>Sat, 17 Jun 2017 17:52:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349028#M11951</guid>
      <dc:creator>arunthomas</dc:creator>
      <dc:date>2017-06-17T17:52:28Z</dc:date>
    </item>
    <item>
      <title>Re: Throttling repeated events</title>
      <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349029#M11952</link>
      <description>&lt;P&gt;A good start would be the search that the "correlation rule" that is running and the schedule that's it is running on.&lt;/P&gt;</description>
      <pubDate>Sat, 17 Jun 2017 22:18:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349029#M11952</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2017-06-17T22:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: Throttling repeated events</title>
      <link>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349030#M11953</link>
      <description>&lt;P&gt;Can you check values of duration and fields to group by for your specific correlation search?&lt;BR /&gt;
&lt;span class="lia-inline-image-display-wrapper" image-alt="alt text"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/3071iC8E5EDC019B1220B/image-size/large?v=v2&amp;amp;px=999" role="button" title="alt text" alt="alt text" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jun 2017 10:30:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Throttling-repeated-events/m-p/349030#M11953</guid>
      <dc:creator>hardikJsheth</dc:creator>
      <dc:date>2017-06-20T10:30:22Z</dc:date>
    </item>
  </channel>
</rss>

