Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
Including Priority Information in System Log Messages
The facility and severity level of a message are together referred to as its priority. By default, messages logged in the standard Junos OS format do not include information about priority. To include priority information in standard-format messages directed to a file, include the explicit-priority statement at the [edit system syslog file filename] hierarchy level:
 | Note: Messages logged in structured-data format include priority information by default. If you include the structured-data statement at the [edit system syslog file filename] hierarchy level along with the explicit-priority statement, the explicit-priority statement is ignored and messages are logged in structured-data format. For information about the structured-data statement, see Logging Messages in Structured-Data Format. For information about the contents of a structured-data message, see the Junos OS System Log Messages Reference. |
To include priority information in messages directed to a remote machine or the other Routing Engine, include the explicit-priority statement at the [edit system syslog host (hostname | other-routing-engine)] hierarchy level:
| Note: The other-routing-engine option does not apply to the QFX Series. |
The priority recorded in a message always indicates the original, local facility name. If the facility-override statement is included for messages directed to a remote destination, the Junos OS system logging utility still uses the alternative facility name for the messages themselves when directing them to the remote destination. For more information, see Changing the Alternative Facility Name for Remote System Log Messages.
When the explicit-priority statement is included, the Junos OS logging utility prepends codes for the facility name and severity level to the message tag name, if the message has one:
(The tag is a unique identifier assigned to some Junos OS system log messages; for more information, see the Junos OS System Log Messages Reference.)
In the following example, the CHASSISD_PARSE_COMPLETE message belongs to the daemon facility and is assigned severity info (6):
When the explicit-priority statement is not included, the priority does not appear in the message:
For more information about message formatting, see the Junos OS System Log Messages Reference.
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
Published: 2013-08-09
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
