[Contents] [Prev] [Next] [Index] [Report an Error]

Specifying the Facility and Severity of Messages to Include in the Log

Each system log message belongs to a facility, which is a group of messages that are either generated by the same software process or concern a similar condition or activity (such as authentication attempts). Each message is also preassigned a severity level, which indicates how seriously the triggering event affects routing platform functions.

When you configure logging for a facility and destination, you specify a severity level for each facility. Messages from the facility that are rated at that level or higher are logged to the destination:



[edit system syslog]
(console | file filename | host destination | user username) {

facility severity;
}

(For information about the destinations, see Directing Messages to a Log File, Directing Messages to a User Terminal, Directing Messages to the Console, and Directing Messages to a Remote Machine or the Other Routing Engine.)

To log the messages belonging to more than one facility to a particular destination, specify each facility name as a separate statement within the set of statements for the destination.

Table 19 lists the JUNOS system logging facilities that you can specify in configuration statements at the [edit system syslog] hierarchy level.

Table 19: JUNOS System Logging Facilities

Facility	Type of Event or Error
any	All (messages from all facilities)
authorization	Authentication and authorization attempts
change-log	Changes to the JUNOS configuration
conflict-log	Specified configuration is invalid on the routing platform type
daemon	Actions performed or errors encountered by system processes
dfc	Events related to dynamic flow capture
firewall	Packet filtering actions performed by a firewall filter
ftp	Actions performed or errors encountered by the FTP process
interactive-commands	Commands issued at the JUNOS command-line interface (CLI) prompt or by a client application such as a JUNOScript or NETCONF client
kernel	Actions performed or errors encountered by the JUNOS kernel
pfe	Actions performed or errors encountered by the Packet Forwarding Engine
user	Actions performed or errors encountered by user-space processes

Table 20 lists the severity levels that you can specify in configuration statements at the [edit system syslog] hierarchy level. The levels from emergency through info are in order from highest severity (greatest effect on functioning) to lowest.

Unlike the other severity levels, the none level disables logging of a facility instead of indicating how seriously a triggering event affects routing functions. For more information, see Disabling Logging of a Facility.

Table 20: System Log Message Severity Levels

Severity Level	Description
any	Includes all severity levels
none	Disables logging of the associated facility to a destination
emergency	System panic or other condition that causes the routing platform to stop functioning
alert	Conditions that require immediate correction, such as a corrupted system database
critical	Critical conditions, such as hard errors
error	Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels
warning	Conditions that warrant monitoring
notice	Conditions that are not errors but might warrant special handling
info	Events or nonerror conditions of interest

[Contents] [Prev] [Next] [Index] [Report an Error]