Comments
6 comments
-
Hi and thanks for trying the beta
We don't currently have an explicit "Agent not running" incident, but at the next scheduled job run you should be getting a "Job failed to start (Agent not running)" -
I would also concur that adding an "Agent not running" incident would be a nice addition to the feature set.
-
Thanks for your feedback.
Would you say this is useful even if you have no jobs scheduled to run on that server?
Since, if there are jobs scheduled to run, then if the Agent is not running, you will be told the agent is not running - via "Job failed to start (Agent not running)" incident per job. -
If there were no jobs, then the Agent Not Running incident would have not much value. Getting the "Job failed to start" incident is good and does provide a minimum level of alerting the Agent is perhaps not running, but take the following scenario:
Somehow Agent is disabled/turned off at 2pm. You're next scheduled job is 1am. The "Job failed to start" incident would fire at 1am and it would be possible to respond and fix it, however, why should I have to wait until 1am and get woken up, when I could have found out Agent wasn't working 11 hours earlier and easily fixed it while I was at my computer. -
Thanks for that, that's a good point. We're very interested in which incident types are good, which are bad, and any that are missing.
All the best,
Dan Archer
Red Gate Software -
I think it's useful to know if any SQL-related services are not running that should be (e.g., SSIS, SSAS, Browser, Full-text). I have a custom report for this now but there is no alert feature to it. For your product, I would default to if it's installed, assume it should be running. If not, DBA can indicate ignore for this server.
Add comment
Please sign in to leave a comment.
-jfc-