SQL probe agent_job_failure not creating an alert in USM under any severity setting
Article ID: 103959
Updated On:
Products
NIMSOFT PROBES
DX Infrastructure Management
Issue/Introduction
The sqlserver probe will not generate an alarm for agent_job_failure checkpoint in USM under any severity setting.
Cause
- Working as designed, see KB Article:
How does the sqlserver "agent_job_failure" checkpoint work?
https://knowledge.broadcom.com/external/article?articleId=34961
Environment
- UIM 8.51
- sqlserver (any version)
- sqlserver (any version)
Resolution
Customer decided to use an alternative to alarm on sqlserver agent job failures.
Since SQL job failures write an event ID 208 to the application file, the customer chose to setup the ntevl probe for the applicable devices with the specific criteria/messages for each job they needed to alert on. This is an excellent and very straightforward alternative and you can use the ntevl probe profiles to alarm on individual job failures and their associated alarm messages,.
Since SQL job failures write an event ID 208 to the application file, the customer chose to setup the ntevl probe for the applicable devices with the specific criteria/messages for each job they needed to alert on. This is an excellent and very straightforward alternative and you can use the ntevl probe profiles to alarm on individual job failures and their associated alarm messages,.
Event ID: 208 Source: SQLSERVERAGENT
Source
Level
Description (example)
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan '<name of job>' (0xF673402DE6B2F14A9C671B08202C92E2) - Status: Failed - Invoked on: 7/10/2001 12:15:00 AM - Message: The job failed. Unable to determine if the owner (<username>) of job DB Backup Job for DB <name of job>' has server access (reason: Could not obtain information about Windows NT group/user '<name of user>'. [SQLSTATE 42000] (Error 8198)).
Feedback
Powered by
