Job duration taking too long - triggering WHILE job is still running
CONTEXT: If a job is taking a long time (outside of some predefined threshold), we want to be alerted about it. That’s often an actionable alert – we could decide to stop the job, we could let the users know that report XY will be late as a consequence etc. One step further is being alerted on the job STEP level as well.
PROBLEM: Current alert “Job duration unusual” is triggered AFTER the job completes, if it meets the alert's criteria. We need an alert to trigger WHILE the job (or job step) is still running, but the criteria is already met.
• Change the “Job duration unusual”
• New alert(s)
Thanks Blaž, that makes sense - I'll merge the suggestions and discuss this with the team
Blaž Dakskobler commented
Please move these votes over to https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/33919051-job-duration-taking-too-long-triggering-while-jo , which currently has 44 votes already.
Currently I don't have an option to get alerted if we want to know if a job is hung, been running for a long time and has been stuck?
SQL Monitor only offers the option to get alerted AFTER a job is finished with an unusual duration.
In case I have a job running usual a few minutes, but sometimes stuck during the execution which tends to much longer runtime. This won't be spotted by SQL Monitor.
Please, add a new alert to address such issues.
Or you could get a better scheduler such as JAMS from MVPSI, which can send alerts on 'over run', or take some other action (like kill the job).