Job duration unusual - Baseline incorrectly calculated

Andrew Hodge

Just installed SQL response for evaluation and testing and getting a low priority alert for Job duration unusual which seems to be because the baseline duration has been incorrectly calculated. The last 10 runs show a duration of 19s, 20s, 22s, 19s, 20s, 20s, 19s, 22s, 21s and 21s but the baseline duration calculated is 250.20s, the current run duration is 21.00s? The average of the above 10 jobs is 20.3s?

See link for screenshot of issue

http://net2005.myby.co.uk/sqlresponse.png

Thanks

Andrew

Isobel Hooper

I agree, that baseline calculation does seem to be rather out.

Thank you for letting us know about this - one of our developers is off today, but he will have a look at it tomorrow and we will see if we can reproduce it.

Andrew Hodge

Another occurrence of this problem on a different job

Andrew Hodge

And another

Isobel Hooper

Thank you for the further examples - we have logged it in our bug track system.

dlkj

Hi Andrew,

I've managed to reproduce the issue and I'm currently working on a fix.

Thanks for your help.
--
Daniel

laker_42

Daniel,
Any idea when we can expect a fix for this? I am experiencing the same issue

John

dlkj

Hi John, Andrew,

I've submitted a fix for this issue. Once this has be tested, it should be included in a point release hopefully some time next month.

Cheers,
--
Daniel

Eddie D

SQL Response Version 1.1 has fixed this particular problem.

Many Thanks
Eddie