those values. In standard format, the variables are interspersed in the message text and
not identified as variables.
The structured-data format for a message includes the following fields (which appear
here on two lines only for legibility):
<priority code>version timestamp hostname process processID TAG [junos@2636.platform
variable-value-pairs] message-text
Table 15 on page 37 describes the fields. If the system logging utility cannot determine
the value in a particular field, a hyphen ( - ) appears instead.
Table 15: Fields in Structured-Data Messages
ExamplesDescriptionField
<165> for a message from
the pfe facility
(facility=20) with
severity notice
(severity=5).
Number that indicates the message’s
facility and severity. It is calculated by
multiplying the facility number by 8 and
then adding the numerical value of the
severity. For a mapping of the numerical
codes to facility and severity, see Table:
Facility and Severity Codes in the
priority-code Field in “Specifying the
Facility and Severity of Messages to
Include in the Log” on page 8.
<priority code>
1 for the initial versionVersion of the Internet Engineering Task
Force (IETF) system logging protocol
specification.
version
2007-02-15T09:17:15.719Z
is 9:17 AM UTC on 15
February 2007.
2007-02-15T01:17:15.719
-08:00 is the same
timestamp expressed as
Pacific Standard Time in
the United States.
Time when the message was generated,
in one of two representations:
•
YYYY-MM-DDTHH:MM:SS.MSZ is the
year, month, day, hour, minute,
second and millisecond in Universal
Coordinated Time (UTC)
•
YYYY-MM-DDTHH:MM:SS.MS+/-HH:MM
is the year, month, day, hour, minute,
second and millisecond in local time;
the hour and minute that follows the
plus sign (+) or minus sign (-) is the
offset of the local time zone from UTC
timestamp
router1Name of the host that originally
generated the message.
hostname
mgdName of the Junos process that
generated the message.
process
3046UNIX process ID (PID) of the Junos
process that generated the message.
processID
UI_DBASE_LOGOUT_EVENTJunos system log message tag, which
uniquely identifies the message.
TAG
37Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages