The last x runs at the same time of day is pretty much a must have to get rid of false positives. Here is the most common one we run into: pretty much every SQL Server instance gets some variation of an hourly log backup job and a weekly index maintenance job. Of course the log backup after the index maintenance job always throws an alert since it take longer than the median of the last 10 runs.
We can work around this specific example with a maintenance window but this is just a simple case. It would be really helpful to be able to alert and report on job duration by time of day.
The last x runs at the same time of day is pretty much a must have to get rid of false positives. Here is the most common one we run into: pretty much every SQL Server instance gets some variation of an hourly log backup job and a weekly index maintenance job. Of course the log backup after the index maintenance job always throws an alert since it take longer than the median of the last 10 runs.
We can work around this specific example with a maintenance window but this is just a simple case. It would be really helpful to be able to alert and report on job duration by time of day.