Alerting

Prevent Duplicate Alerts

mayfieldm
New Member

We have an alert that searches our databases for unknown/missing columns or tables. The search runs on an hourly basis, and sends an email if the condition is triggered. The issue we're running into is sometimes we don't have an opportunity to fix the missing column/table before the next hour goes by and the alert gets triggered again--leading to multiple emails for the same issue. We want to basically stop duplicate emails/duplicate triggers. I have read about throttling and that does not seem to be the fix we're looking for. In SQL terms, we'd be wanting an 'if/else' statement... if this missing column/table has already sent an email, don't send again. else, send. any thoughts would be appreciated!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...