One of the most common alerts that we get is the Long Running Query alert. However, when the query is due to a package executing from an agent job, there is little to no information about what is running long. The attached image is an excerpt from one of the alerts we got this morning. We can tell it is from an executing job, because of the SSISDB database specified. But beyond that, we are left trying to figure out which job/package was the culprit by digging through execution logs and schedules, then trying to match execution lengths with where the alert would have been triggered. Maybe in a future release you can maybe add which package is executing that triggered the alert.
Comments
3 comments
-
Hi @VBJV this has been asked before, but I'm afraid we don't yet support this. I recommend that you head over to the SQL Monitor Uservoice and request it there, as we use this to prioritise future feature work. -
When I go over to redgate.uservoice.com, there's no way to add a request/idea. SQL Monitor doesn't even show up in the list on the right hand side of the screen.
-
Sorry, I thought I'd given you the link in the post above but obviously forgot, let me edit it..
Add comment
Please sign in to leave a comment.