Configuring Log Severity For Individual And Systemwide Logs - Juniper JUNOSE 11.1.X - SYSTEM EVENT LOGGING REFERENCE GUIDE 3-24-2010 Reference Manual

JUNOSe 11.1.x System Event Logging Reference Guide
log unlimit
log verbosity

Configuring Log Severity for Individual and Systemwide Logs

You can change the severity setting for individual logs and the systemwide value.
When working with log severities, keep the following in mind:
10
Configuring Log Severity for Individual and Systemwide Logs
Use to remove the limit on the number of outstanding buffers for an event
category, such as when the system is dropping logs of a particular category.
Example
host1(config)#log unlimit qos
Use the no version to return to the default value.
See log unlimit.
Use to set the verbosity level for a selected category or for all categories.
If you do not specify a category, then the verbosity level is set for all categories.
The default verbosity setting for all logs is low.
Example
host1(config)#log verbosity low
Use the no version to return to the default verbosity (low) for the selected
category.
See log verbosity.
All log event categories have a default. However, the default values can vary for
each category. For example, most event categories have a default severity of
Error. However, some event categories may have a default severity of Notice,
Warning, Info, and so on.
Log event categories have two states unassigned (default) and assigned. How
a log event category reacts to the log severity command depends on its current
state.
You can change log severities for event categories at a systemwide level or an
individual level. Systemwide changes are those that modify a large number of
unassigned event categories at one time; for example, the command log severity
debug off. Individual changes are those that indicate an explicit event category
that you want to change; for example, the command log severity notice
clicommand.
Changes to log event categories at an individual level take precedence over those
made at the systemwide level.
Changes to log event categories at the systemwide level take precedence over
the default.
Assigning a log severity to an individual event category changes its state to
Assigned. This means that you cannot change the severity of that event category