Event priorities are shown in Table 8-3. EVM priorities range from 0-700, with 700 intended to be the highest priority, whereas syslog priorities range from 7-0, with 0 (zero) being the highest. The binlog priority range, with only three effective priorities, is not nearly as granular.
Event Priorites | |||
---|---|---|---|
Name | EVM | syslog | binlog |
process-to-process | 0 | - | low (5) |
debug | 1-99 | 7 | |
information | 100-199 | 6 | |
notice | 200-299 | 5 | high (3) |
warning | 300-399 | 4 | |
error | 400-499 | 3 | |
critical | 500-599 | 2 | severe (1) |
alert | 600-699 | 1 | |
emergency | 700 | 0 |
The EVM priority of zero is reserved for events that are not to be viewed by anyone. These low priority events are useful for applications to communicate amongst themselves, such as a heartbeat event from another process to keep itself alive (as you will see in the NetRAIN Events section [chapter 9, section 9.2.3], all the registered events have a priority of zero). By default, events lower than a priority of 200 are not logged by the EVM logger.
The EvmEvent(5) reference page lists the EVM priorities and their intended use.