Table of Contents
Advertisement
Including the Year or Millisecond in Timestamps
Copyright © 2010, Juniper Networks, Inc.
Table 10: Numerical Codes for Severity Levels Reported in Priority
Information (continued)
Numerical Code
4
5
6
7
In the following example, the
facility and is assigned severity
daemon
Aug 21 12:36:30 router1 chassisd[522]:
%DAEMON-6-CHASSISD_PARSE_COMPLETE: Using new configuration
When the
statement is not included, the priority does not appear in the
explicit-priority
message:
Aug 21 12:36:30 router1 chassisd[522]: CHASSISD_PARSE_COMPLETE: Using new
configuration
For more information about message formatting, see "Displaying and Interpreting System
Log Message Descriptions" on page 47.
By default, the timestamp recorded in a standard-format system log message specifies
the month, date, hour, minute, and second when the message was logged, as in the
following example:
Aug 21 12:36:30
To include the year, the millisecond, or both in the timestamp, include the
statement at the [
edit system syslog
edit system syslog]
time-format (year | millisecond | year millisecond);
The modified timestamp is used in messages directed to each destination configured by
a
,
, or
statement at the [
file
console
user
destinations configured by a
Chapter 1: Configuring System Log Messages
Severity Level
warning
notice
info
debug
CHASSISD_PARSE_COMPLETE
:
info (6)
] hierarchy level:
edit system syslog
statement.
host
Description
Conditions that warrant
monitoring
Conditions that are not errors
but might warrant special
handling
Events or nonerror conditions
of interest
Software debugging messages
(these appear only if a
technical support
representative has instructed
you to configure this severity
level)
message belongs to the
time-format
] hierarchy level, but not to
21
Hide quick links:
Advertisement
Table of Contents
