-
Title
Oracle alert log filtering precedence -
Description
When setting up the alert.log filtering, which list takes precedence? Is there a specific order of precedence for the match list and the ignore list? -
Resolution
The ignore list has precedence over the match list and the high severities have precedence over the low severities.
Example 1:
If there are two expressions that return TRUE, then the one with the highest severity will be fired first:
ORA-** is defined as warning
ORA-29913 is defined as critical
When the two above examples are found for the same item within the alert.log and are found to be true, then the alarm will file on the critical alarm.
Example 2:
Imagine the following scenario's setup:
ORA-16* defined in the ignore list
ORA-* is defined within the match list
If you get a message like "ORA-01652 : Unable to extend temp segment by xxxx in tablespace system" is written within the alert log, Foglight will will not fire an alarm although the "ORA-*" expression is TRUE. The reason for this is that the expression "ORA-16*" is within the ignore list and therefore Foglight will not fire an alarm, because the ignore list has precedence over the match list.