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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...