SQL Server Error log alarms do not fire (4230073)

CAUSE 1

Incorrect setting for the minimal severity for triggering alarms

CAUSE 2

Incorrect alarm sensitivity settings

CAUSE 3

The same Error log filter value was added to both the Match list and the Ignore list.

CAUSE 4

Error log collection fails due to Chinese character set on the host OS

RESOLUTION 1

1. Navigate to the Database Dashboard
2. Select one or more SQL Server database agents
3. Click Settings | Administration
4. Click the Error Log Filtering area
5. Set the appropriate minimal severity for triggering alarm or specify "OFF" to disable that alarm type.
   
6. Click the Save changes button

RESOLUTION 2

Check alarm sensitivity levels to make sure the alarms you are expecting to see are enabled as described in KB 133655

RESOLUTION 3

Review the Error log filter values to confirm that conflicting match and ignore values are not present.
Details on using the SQL Server Error Log Filter can be found in KB 69941.

RESOLUTION 4

This issue for the Chinese character set support is listed as known issue SSFOG-770 and is planned to be fixed in a future release of the SQL Server cartridge.