Comments
Sort by recent activity
Another issue I'm noticing.
I have a job right now that has been running for 12 hours. The job is noticeably broken (usually takes 3-4 minutes), and our vendor for that piece of software is investigating the issue. SQL Response has correctly identified that the job duration is, indeed, unusual.
However, the job hasn't completed yet. I while I see the "Job duration unusual" event type, and the detail is correct, but all I can see for details is "This incident is still being written to". Which isn't terribly helpful. While I do know what's going on in this particular case, that's not enough information for me to act on in most circumstances. What I'd like to see is "the job started at 11:35 pm last night, it's still going, do something you idiot" instead of "This incident is still being written to."
chris. / comments
Another issue I'm noticing.
I have a job right now that has been running for 12 hours. The job is noticeably broken (usually takes 3-4 minutes), and our vendor for that piece of software is invest...