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.
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?