<?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 Prevent repeated alerts on recurring results in Alerting</title>
    <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569207#M13058</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I've recently been tasked with alerting our support email when a user in Salesforce is locked out.&amp;nbsp; The alert triggers when a User's &lt;STRONG&gt;LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT"&lt;/STRONG&gt;.&amp;nbsp; However, this alert keeps getting triggered if an admin doesn't unlock the User account right away.&amp;nbsp; Is there any way to limit the alert being sent out if the Usernames are identical as the previous alert?&lt;/P&gt;&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;index="salesforce" EVENT_TYPE="Login" LOGIN_STATUS=* &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;[search EVENT_TYPE="Login" LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count by USER_ID &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| table USER_ID] &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats latest(LOGIN_STATUS) AS LOGIN_STATUS &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(USER_NAME) AS USER_NAME &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(SOURCE_IP) AS SOURCE_IP &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(UserAccountId) AS "Account Id" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(USER_TYPE) AS "User Type" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(TIMESTAMP) AS "Time stamp" by USER_ID &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| where LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT"&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 30 Sep 2021 18:35:17 GMT</pubDate>
    <dc:creator>calejohn5</dc:creator>
    <dc:date>2021-09-30T18:35:17Z</dc:date>
    <item>
      <title>Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569207#M13058</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I've recently been tasked with alerting our support email when a user in Salesforce is locked out.&amp;nbsp; The alert triggers when a User's &lt;STRONG&gt;LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT"&lt;/STRONG&gt;.&amp;nbsp; However, this alert keeps getting triggered if an admin doesn't unlock the User account right away.&amp;nbsp; Is there any way to limit the alert being sent out if the Usernames are identical as the previous alert?&lt;/P&gt;&lt;P class="lia-align-justify"&gt;&lt;STRONG&gt;index="salesforce" EVENT_TYPE="Login" LOGIN_STATUS=* &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;[search EVENT_TYPE="Login" LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats count by USER_ID &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| table USER_ID] &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| stats latest(LOGIN_STATUS) AS LOGIN_STATUS &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(USER_NAME) AS USER_NAME &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(SOURCE_IP) AS SOURCE_IP &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(UserAccountId) AS "Account Id" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(USER_TYPE) AS "User Type" &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;latest(TIMESTAMP) AS "Time stamp" by USER_ID &lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;| where LOGIN_STATUS="LOGIN_ERROR_PASSWORD_LOCKOUT"&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Sep 2021 18:35:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569207#M13058</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-09-30T18:35:17Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569251#M13059</link>
      <description>&lt;P&gt;Turn on throttling.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="richgalloway_0-1633047320650.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/16233i2EFD009E14DDC677/image-size/medium?v=v2&amp;amp;px=400" role="button" title="richgalloway_0-1633047320650.png" alt="richgalloway_0-1633047320650.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 00:15:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569251#M13059</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-01T00:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569342#M13060</link>
      <description>&lt;P&gt;When I add Throttling does that suppress alerts ONLY for that user?&amp;nbsp; Because I want it to continue to alert for different users getting locked out while that initial locked user is locked out&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 14:05:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569342#M13060</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-01T14:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569354#M13061</link>
      <description>&lt;P&gt;If the alert is triggered once then the throttle applies to all instance of that alert for the throttle period.&lt;/P&gt;&lt;P&gt;If the alert is triggered once per result then you can specify a throttle condition.&amp;nbsp; See&amp;nbsp;&lt;A href="https://community.splunk.com/t5/Alerting/Suppress-results-containing-field-value-with-multiple-values/m-p/507816" target="_blank"&gt;https://community.splunk.com/t5/Alerting/Suppress-results-containing-field-value-with-multiple-values/m-p/507816&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 15:20:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569354#M13061</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-01T15:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569364#M13062</link>
      <description>&lt;P&gt;Ok I turned on For Each Result and Suppressing when&amp;nbsp;&lt;STRONG&gt;USER_ID= $result.USER_ID$&lt;/STRONG&gt;.&amp;nbsp; I just need to wait for this query to run again and get indexed and I'll see if that works.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Oct 2021 15:53:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569364#M13062</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-01T15:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569571#M13074</link>
      <description>&lt;P&gt;It seemed to not send out any alerts...&lt;/P&gt;&lt;P&gt;Is there any way to index data from another instance faster?&amp;nbsp; The data doesn't seem updated when I search for event I know recently happened.&amp;nbsp; This would help with testing 10-fold.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Oct 2021 15:32:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569571#M13074</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-04T15:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569584#M13075</link>
      <description>&lt;P&gt;I don't know why no alerts would be sent unless none were triggered.&lt;/P&gt;&lt;P&gt;Tell us more about your other request.&amp;nbsp; What do you mean by "index data faster"?&amp;nbsp; What is the other instance?&amp;nbsp; What is the data flow?&lt;/P&gt;</description>
      <pubDate>Mon, 04 Oct 2021 17:15:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569584#M13075</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-04T17:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569591#M13076</link>
      <description>&lt;P&gt;When I hit "Open in Search" for the alert it brings me to the search, except it's timeframe is "Last 1 hour" while the actual search I built this alert from is based off "All Time".&lt;/P&gt;&lt;P&gt;The "Last 1 hour" timeframe doesn't yield any results whereas the "All Time" search yields a result, which would trigger the alert.&lt;/P&gt;&lt;P&gt;So maybe this search already limits this return result to one time...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But in regards to my last request - Whenever I perform an event in Salesforce, it takes about 8 hours for that event to get added into Splunk.&amp;nbsp; This makes testing extremely difficult.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Oct 2021 18:32:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569591#M13076</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-04T18:32:41Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569689#M13086</link>
      <description>&lt;P&gt;I think the "open in search" link uses the default time window for your system.&amp;nbsp; Manually adjust it to the desired window.&lt;/P&gt;&lt;P&gt;The problem with getting data from Salesforce warrants a new question.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Oct 2021 12:45:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569689#M13086</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-05T12:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569919#M13096</link>
      <description>&lt;P&gt;Ok that makes sense and I tried researching why my data was taking so long to enter Splunk from Salesforce but gave up.&amp;nbsp; It's not a big deal as I just need to fix this one alert anyway.&lt;/P&gt;&lt;P&gt;I was thinking - If I chose &lt;STRONG&gt;number of results rises by '1'&amp;nbsp;&lt;/STRONG&gt;for the trigger condition, wouldn't that send out an individual alert every time a new event (user lockout) occurs, and never again for the same result since the count would remain the same?&lt;/P&gt;&lt;P&gt;I'm testing that out, but as I said earlier it may take awhile.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 16:36:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569919#M13096</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-06T16:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569921#M13097</link>
      <description>&lt;P&gt;I have not tried the "rises by 1" option so I don't know if it will help or not.&amp;nbsp; Please report your findings.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2021 16:54:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/569921#M13097</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-10-06T16:54:12Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent repeated alerts on recurring results</title>
      <link>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/570075#M13099</link>
      <description>&lt;P&gt;I ran out of time to properly test "rise by 1".&amp;nbsp; I couldn't even get&amp;nbsp;&lt;STRONG&gt;$result.USER_ID$&lt;/STRONG&gt; in the alert message to work.&lt;/P&gt;&lt;P&gt;I ended up just triggering for each result and suppressing the alert for 24 hours.&amp;nbsp; If anything I'll have to come back in the future and learn more/work on this.&amp;nbsp; I appreciate the help!&lt;/P&gt;</description>
      <pubDate>Thu, 07 Oct 2021 14:27:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Alerting/Prevent-repeated-alerts-on-recurring-results/m-p/570075#M13099</guid>
      <dc:creator>calejohn5</dc:creator>
      <dc:date>2021-10-07T14:27:03Z</dc:date>
    </item>
  </channel>
</rss>

