Delay firing "DBSS - Jobs Failed alarm" (4309769)

Delay firing "DBSS - Jobs Failed alarm"

Jobs are failing on monitored servers, but the DBSS alarm is not firing shortly after the job fails when expected. Collections are working as the SQL Agent Jobs view displays the known failed jobs. Failed Jobs Alarms may be fired for some SQL agents as seen in the Alarms dashboard(current or historical).

Default Collection frequency for "Agent Job List" was at the default Offline value of 3600s (1hr). In this case when a SQl Agent Job fails, it can be up to 1 hour before a Console Alarm or Email Notification fires unless there is a console user logged in. When a FMS Console user is logged in the collection frequency is either 5 minutes, or 60 seconds when on certain Realtime views.

Reduce the "Agent Job List" Offline collection frequency to 300 seconds and set the Alarms view to refresh in 60 seconds in order for console users to see the failures sooner.

1. On the Database Dashboard, place a check mark next to the agent or agents to be modified.
2. Click Agent Settings | Administration.
3. Select the Collection Frequencies tab.
4. Highlight the "Agent Job List" Collection.
5. Click the Edit button.
6. Modify the Offline Frequency: field to be less than 3600. Example: 300.
7. Click the Set button.
8. Click Save Changes.
9. Optionally change the Alarms Dashboard refresh interval to 60s.
10. Validate by failing a test job on the instance and noteing the Alarm or Email Notification now appears in a more timely manner.