-
Title
Can severity levels be set for SQL Server Error Log filters? -
Description
Is it possible to change the severity of the keywords in the matching list?If a new keyword is added to the matching list, which severity will it have?Can the severity for each SQL Server Error Log filter level be changed to make the alarm more sensitive?- Adding a new filter keyword and also severity.
- Deleting an existing filter keyword.
- Editing an existing filter keyword and also severity..
- After adding or editing a filter keyword and severity, a new alarm will raise with new filter keyword and severity.
-
Cause
In SQL Server, the Error Log filtering administration screen allows configuring the default display filters for the Error Log drilldown. These filters determine which error messages are displayed under each of the panes and not the alarms.
The alarms severity level is based on the error code that is in the SQL Server error log message. The functionality does not set a specific severity level per filter.
-
Resolution
If a new SQL Server Error Log filter matching a message that is a Severity 16, then a Warning Alarm will fire.
X/X/XX 7:45 AM Backup Error: 18210, Severity: 16, State: 1.
X/X/XX 7:45 AM Backup BackupIoRequest::ReportIoError: write failure on backup device 'F:\TLSHipBKUPS\test_JS_20170524104501.trn'. Operating system error 112(There is not enough space on the disk.).If the SQL Server Error Log filter matches a message that is a Severity 24, then a Fatal Alarm will fire.X/X/XX 7:46 AM spid51 Error: 824, Severity: 24, State: 2.
X/X/XX 7:46 AM spid51 SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:43686; actual 0:0). It occurred during a read of page (1:43686) in database ID 23 at offset 0x0000001554c000 in file ''F:\TLSHipBKUPS\test_JS_20170524104631.trn'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.If a new keyword is added to the matching list, it is likely to be Information (no alarm) or warning because the Severity 17-25 items are already defined so a keyword that matches would already fire an alarm because of the severity number.
STATUS
A Enhancement Request has been created to get more fexibility in the Error Log filtering for SQL Server. The ER number is FOG-219. The request is to implement the same features / flexibility like the Oracle cartridge provides for alert log filtering.
-
Defect ID
FOG-219