Before configuring and monitoring system log messages on Services Routers, become familiar with the terms defined in Table 77.
Table 77: System Log Message Terms
|
Term |
Definition |
|---|---|
|
event |
Condition that occurs on a Services Router at a particular time. An event can include routine, failure, error, emergency or critical conditions. |
|
event ID |
System log message code that uniquely identifies a system log message. The code begins with a prefix indicating the software process or library that generates the event. |
|
facility |
Group of messages that either are generated by the same software process (such as accounting statistics) or concern a similar condition or activity (such as authentication attempts). For a list of system logging facilities, see Table 78. |
|
priority |
Combination of the facility and severity level of a system log message. By default, priority information is not included in system log messages, but you can configure the JUNOS software to include it. For more information, see the JUNOS System Log Messages Reference. See also facility; severity level. |
|
process |
Software program, also known as a daemon, that controls router functionality. The following are some key JUNOS processes:
For more information about processes, see the JUNOS Software Installation and Upgrade Guide. |
|
process ID |
Identifier uniquely identifying a process. The process ID is displayed in a system log message along with the name of the process that generates the event. |
|
regular expressions |
Set of key combinations that allow you to have control over what you are searching. You can use regular expressions to filter system log messages by specifying a text string that must (or must not) appear in a message for the message to be logged. For more information, see Regular Expressions. |
|
severity level |
Measure of how seriously a triggering event affects Services Router functions. For a list of severity levels that you can specify, see Table 79. |