Couple of Options:
You can run a SQL report on your Alerts and then audit them (requires SQL knowledge to interpret the results)
SELECT AlertName ,AlertDescription ,ObjectType ,TriggerQuery ,CASE WHEN ResetQueryDesign = 'Simple' THEN 'RESET WHEN TRIGGER CONDITIONS NO LONGER EXIST' WHEN ResetQuery = '' THEN 'NO RESET FOR TRIGGER EXISTS' ELSE ResetQuery END AS ResetQuery FROM AlertDefinitions WHERE Enabled = 1
Otherwise, I would start with the idea that Vinay BY mentioned and look at your Alert Log through the website. You can filter your results to both alert triggers and alert resets.
One thing I have seen a lot of times: clients have an email action for both the alert trigger and reset. However they leave the subject line for both emails the same. It's very possible to have flawed alert logic that will cause either false positives, or false resets; both of which would result in 2 emails spaced about 1-2 minutes apart for every alert.
To work around this, I would highly recommend that you mark your email subject lines with 'Alert Triggered:______' and 'Alert Reset:_______' just to save some headaches down the road.
Ultimately, the answer to your question is up to you. You could take the time to audit each alert, or you could disable them all and build from scratch. Each would take about the same amount of work to be honest. I would caution that, either way, you should get the foundation logic in place for accurate alerting before spending too much time "running in circles" so to speak.
Perhaps you could post some screenshots of the alerts that you are having problems with to see if there is an easy fix that someone could identify for you? Alert Triggers and Reset Triggers please.
Loop1 Systems: SolarWinds Training and Professional Services
- LinkedIN: Loop1 Systems
- Facebook: Loop1 Systems
- Twitter: @Loop1Systems