"DBSS - Long Running Job" rule alarm does not fire (4311651)

"DBSS - Long Running Job" rule alarm does not fire 

There are two settings affecting the firing of this rule:

A). The rule also has a preconfigured Agent Status Property setting for a minimal number of seconds that the job runs before the alarm is fired.

Editing the minimal job running time for a "Long Running Job Rule"

1. Navigate to Administration | Agents | Agent Status
2. Select a SQL Server database agent
3. Edit the properties for the database agent
4. Select the link to modify the private properties for this agent
5. Scroll down to the Long Running Job Rule section of the ASP (Agent Status Properties)
6. Set the value for The minimal job running time value that 'Long Running Job Rule' will be fire (in seconds).
7. Click the Save Changes button.

B). The "DBSS - Long Running Job" rule is based on using Foglight's Intelliprofile baselining mechanism. 

"An alarm is invoked when a job's execution time proportionately exceeds average execution time by a given threshold. Foglight calculates the average execution time from past execution times for that job. For example, if a job last ran for 10 seconds and the average execution time of that job is 5 seconds, then the job has run longer than usual by 200%.".

This exception duration percentage is controlled by the Alarm Template's "percentage of normal run time" setting for the alarm which may by default set to 125%. This level would cause the alarm to be fired when the job runs 25% longer than the average calculated baseline duration of previous runs of the same job.

For It may be helpful to lower the percentage of normal run time setting in the Alarm Template for testing purposes.