Observer Apex : Observer Apex : Reacting to network events : Understanding log categories
Understanding log categories
Matrix logs hundreds of interactions into one of four log categories: informational, warning, error, and fatal.
Informational messages. They can be queried for trends. No action is required.
Example: New network settings have been applied
Warning messages. They indicate a potential issue. An error might occur if corrective action is not taken in a given time.
Example: Error reading general config file
Error messages. They indicate non-urgent failures. These indicate changes or events that did not match expected results, such as a file could not be opened or program was busy. Typically, these are critical messages and must be addressed by changing some input value before the desired result is achieved or by your device administrator or developer.
Example: Unable to open CLI config file. No such file or directory
Fatal message. These messages indicate an imminent issue that should be corrected immediately, such as during updating the firmware or resetting the system defaults. Contact your support staff.
Example: Unable to apply firmware update!
<STRING> is a variable and may be a: word or words (for example, user name, host name, filter) or a number (for example, port number, version number, group ID).