Interpreting Messages Generated by a JUNOS Process or Library

The syntax of a message generated by a JUNOS software process or subroutine library differs depending on whether it includes priority information:

• When the explicit-priority statement is included at the [edit system syslog file filename] or [edit system syslog host (hostname | other-routing-engine)] hierarchy level, a system log messages has the following syntax:

timestamp     message-source: %facility-severity-tag: message-text 

• When directed to the console or to users, or when the explicit-priority statement is not included for files or remote hosts, a system log message has the following syntax:

timestamp    message-source: tag: message-text

Table 17 describes the message fields.

Table 17: Fields in Messages Generated by a JUNOS Process or Library 

Field	Description
tag	Text string that uniquely identifies the message, in all uppercase letters and using the underscore (_) to separate words. The tag name begins with a prefix that indicates the generating software process or library. The entries in this reference are ordered alphabetically by this prefix. Not all processes on a routing platform use tags, so this field does not always appear. For a list of prefixes for the tags described in this reference, see System Log Messages.
facility	Code that specifies the facility to which the system log message belongs. For a mapping of codes to facility names, see Table 11.
message-source	Identifier of the process or component that generated the message and the routing platform on which the message was logged. This field includes two or more subfields, depending on how system logging is configured. See Format of the message-source Field.
message-text	Text of the message. For the text for each message, see the chapters following System Log Messages.
severity	Numerical code that represents the severity level assigned to the system log message. For a mapping of codes to severity names, see Table 12.
timestamp	Time at which the message was logged.