Comments
Sort by recent activity
Add me up to this request
[MOD] Preferably using windows authentication or some type of mixed mode with role based authorisation on defining permissions.
Also marking as 'read only user' is an important option / comments
Add me up to this request
[MOD] Preferably using windows authentication or some type of mixed mode with role based authorisation on defining permissions.
Also marking as 'read only user' is an impo...
agree with this request / comments
agree with this request
We're running 2.2.0.260 and this seems to still occur.
My alert settings for 'Job duration unusual' are:
high 70%, medium 60%, low 50%
all enabled
Ignore if the job run time is less than 60 seconds
Now I received a high alert with this data:
Job name: SQL Backup TL 2130 to 1830
User: <domain user here>
Job started at: 9 Mar 2011 7:30 AM
Job ended at: 9 Mar 2011 7:30 AM
Job outcome: Succeeded
Duration: 00:00:08
Baseline duration (median of last 10 runs): 00:01:10
Deviation from baseline: -89%
Job next scheduled to run at: 9 Mar 2011 10:30 AM
As you can see duration is (much) less than 60 seconds, so no alert should have been raised at first place I guess. -89% is interpreted as 89% deviation, which is OK (I already posted a feature request to be able to exclude negative deviations) / comments
We're running 2.2.0.260 and this seems to still occur.
My alert settings for 'Job duration unusual' are:
high 70%, medium 60%, low 50%
all enabled
Ignore if the job run time is less than 60 seconds...