Comments
3 comments
-
Official commentHi emmar00
You're certainly correct that even though clearing them removes them from the view, the underlying issue which caused the alert to appear most likely hasn't been resolved. You can also see the history of occurrences of said alert by opening it and viewing the ‘History’ tab. This might give you a better picture of why the alert is failing.
Until the root cause is found and resolved, the alert will likely stay as ‘Active’.
-
I also noticed the same behavior with alerts. I had a job failed and I cleared it, and now I do not get that alert anymore. Shouldn't the alert be raised next time the job fails? That is what used to happen in previous versions. Really disappointed with this change.
-
I have discovered that if the job is deleted, the alert will close. Disabling the job is not sufficient. (I assume this is based on viewable data in msdb that is no longer present after deleting the job.)
I don't love it, but it does feel correct (there are no longer failed runs of job X). Plus, if the job isn't going to run again, does it really need to stay created out there? If not, maybe script it out and save it to disk or turn it into a more ad-hoc script (like a SQL Prompt snippet).
Add comment
Please sign in to leave a comment.
When I look at the “Job failure” alerts that have not Ended, I see there are quite a few “one off” jobs. Maybe these jobs were just from personal testing or maybe it was a one-time configuration job that failed partway through and the rest was carried out by hand. Either way, the job's not going to run on that server any time soon. But it's still an active issue in Monitor. I have these events Cleared to get them off the primary dashboard, but that doesn't mean that they aren't a problem. (In fact, the whole reason I'm running this report is to look for jobs that were mistakenly cleared but are still failing, meaning they do need attention.)