Alerting

Alert throttling resets

cyberbilliam
Loves-to-Learn Lots

So we have a search creating a notable event.  The search is configured to suppress for 2 days.  The search is managed in an a Splunk app.  If we install a new version of the app, or make any changes to the search, the throttle appears to be reset.

My question is if it is possible to preserve the throttling  between app installs or changes to the search?  Ultimately what we want to avoid is changes to the app causing duplicate notable events from being created.

Labels (2)
0 Karma

cyberbilliam
Loves-to-Learn Lots

So @jwelch_splunk I was looking at https://community.splunk.com/t5/Alerting/Alert-suppression-List-throttled-suppressed-field-values/m-... Thanks for the info on /opt/splunk/var/run/splunk/scheduler/suppression/ as it appears that it may be related to my issue.

Are you aware if this file gets modified when you deploy a new app or change a saved search?

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...