How can we help you today? How can we help you today?
priyasinha
Hi Rhys, Unfortunately this is a Microsoft issue and we cannot do anything about it. http://support.microsoft.com/kb/891238 http://blogs.technet.com/b/rob/archive/ ... ssues.aspx Thanks, Priya / comments
Hi Rhys, Unfortunately this is a Microsoft issue and we cannot do anything about it.http://support.microsoft.com/kb/891238http://blogs.technet.com/b/rob/archive/ ... ssues.aspx Thanks, Priya
0 votes
Thanks John and Oderks for your post. The Job Duration Unusual alert operates in two stages: Firstly we calculate the baseline (using the median of the last 10 runs). If this is less than the short running time threshold, the alert is disabled until the baseline increases again. Once the job is known to take a while, we compare each run against the baseline and alert if it deviates too far away from it. The default configuration thus makes the assumption that a quick running job can be ignored, and once a job is known to take a significant time, it shouldn’t start running quickly or slowly. Ignoring short running jobs is a powerful way to set defaults for a whole server, but it isn’t that useful to be set on an individual job. You know how long the job normally takes, and so can enable or disable alerting on it to taste. The ‘ignore if runtime is less than…’ doesn’t work for the use case where you have a job that (say) copies any available new log files, which will run in less than a second if there is nothing to do but takes several minutes every now and then. We didn’t want to try and automagically figure out what is happening and this case and risk getting it wrong. Hope it explains the behaviour you both are noticing. Thanks, Priya / comments
Thanks John and Oderks for your post. The Job Duration Unusual alert operates in two stages: Firstly we calculate the baseline (using the median of the last 10 runs). If this is less than the short...
0 votes
Hi, Thanks for your feedback. Unfortunately, this is not supported in the current released version. I have logged this enhancement request as SRP-2472. Thanks, Priya / comments
Hi, Thanks for your feedback. Unfortunately, this is not supported in the current released version. I have logged this enhancement request as SRP-2472. Thanks, Priya
0 votes