SQL Agent jobs with a 'cancelled' status are incorrectly flagged as 'Job failing' in the Alert Inbox
With Always On related SQL Agent jobs, an initial job step is added to check whether the target database is Primary/Secondary on the cluster node. If 'Primary', then continue with subsequent job steps, if 'Secondary' then stop and do not attempt any further job steps. In circumstances where the job is stopped the last run outcome is shown as 'Canceled' - however, SQL Monitor shows these particular status jobs as 'Job failing' in the Alert Inbox. The job hasn't really failed and has been stopped in a controlled way. Can the status of these job be correctly identified please?
Thanks for this suggestion, and for the additional comments which helped us decide quickly what solution to implement.
Version 9.0.13 released 23rd May includes a new Job cancelled alert (off by default) and stops the existing Job failing alert being raised for cancelled jobs.
We hope this meets requirements and will mark it as closed, but please do raise further suggestions for any improvements you would like to see.
SQL Monitor Development Team
Option 3 is preferred
Thank you for the feedback Adam. Of the options mentioned, I think option 3 would be preferable. It will still enable all SQL Agent job alerts to come through, but allow easy filter for those which are either cancelled or failed. Once this is implemented, as mentioned in another comment, the additional ability to enable disable each of these alerts per server/instance would also be beneficial. Many thanks.
I'd say that either option 2 or 3 would be great, but there are still times when we'd want a cancelled job alert so I wouldn't like to see the alert completely removed for this ru_status.
There are some instances where we would like to know about a cancelled job, but the majority of our monitoring wouldn't require an alert for run_status 3. If we could have something configurable on a per server/instance that can either enable or disable alerts for stopped/cancelled jobs.