<?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: Rolling time period question in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747526#M11954</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/309204"&gt;@spm807&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as I said, try using throttling in your alerts, it's the solution to your problem.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:36:46 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2025-06-05T06:36:46Z</dc:date>
    <item>
      <title>Rolling time period question</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747468#M11951</link>
      <description>&lt;P&gt;I would like to do a search of a rolling 60-minute period, looking for 3 or more occurrences in that period. I set up a Splunk alert to run every 15 minutes, looking back 1 hour, which works, but then I get multiple alerts for the same 3 events, as they still are in the 60-minute look back period for multiple runs, which happen every 15 minutes. How can I set this up (or code it) so it only reports the 3 occurrences in the previous 60 minutes once?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:28:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747468#M11951</guid>
      <dc:creator>spm807</dc:creator>
      <dc:date>2025-06-04T13:28:27Z</dc:date>
    </item>
    <item>
      <title>Re: Rolling time period question</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747469#M11952</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/309204"&gt;@spm807&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;usually the time period is the same of the execution frequency just to avoid duplicates.&lt;/P&gt;&lt;P&gt;Anyway, you could copnfigure throttling to avoid that the same values fire the alert.&lt;/P&gt;&lt;P&gt;Throttling id configured by the fields in your alert.&lt;/P&gt;&lt;P&gt;In other words, if you have a stats count BY host, you can configure the throttling by host, so if the same host will b e fired the alert will not be triggered.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:37:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747469#M11952</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-06-04T13:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: Rolling time period question</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747470#M11953</link>
      <description>&lt;P&gt;The reason the time period of the execution frequency is not the same as the execution frequency is so we don't miss a 3-event occurrence that straddles two periods. If we ran it once every 60 minutes looking back 60 minutes, we wouldn't get duplicates, but we'd also miss the case in which one event occurred just before the last 60 minutes, and 2 occurred just after the start of the period. I will investigate stats count BY host, thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:45:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747470#M11953</guid>
      <dc:creator>spm807</dc:creator>
      <dc:date>2025-06-04T13:45:10Z</dc:date>
    </item>
    <item>
      <title>Re: Rolling time period question</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747526#M11954</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/309204"&gt;@spm807&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as I said, try using throttling in your alerts, it's the solution to your problem.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:36:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Rolling-time-period-question/m-p/747526#M11954</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-06-05T06:36:46Z</dc:date>
    </item>
  </channel>
</rss>

