I've noticed that some jobs don't raise an alert when they fail. I suspect it has to do with whether or what sort of error code is returned, but so far I've been unable to find the difference between jobs failures that raise the alert and ones that don't.
Here are two examples of recent job failures that didn't raise an alert:
1) transaction log backup failed because it was missing a full backup.
2) DBCC CHECKDB reporting consistency errors for a database.
I've verified that run_status = 0 in sysjobhistory, and that the job step is configured to "quit the job reporting failure" when the step fails. Both jobs are part of Maintenance Plans, but failures of those types of jobs have raised the alert before.
So I really have a two-part question.
First, why aren't these job failures triggering the "job failed" alert? i.e. what's different about them?
Second, and more importantly, how can I get alerts on them in the future? I really do want to know when log backup fail or I have consistency/corruption issues with databases. Basically, if I see a "red X" icon in the job history via SSMS, I think I'd like to get an alert via SQL Monitor.