log-extended Section

This section must be called log-extended.

level-reassign-disable

Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When this option is set to true, the original (default) log level of all log events in the [log-extended] section are restored. This option is useful when you want to use the default levels, but not delete the customization statements.

level-reassign-<eventID>

Default Value: Default value of log event <eventID>
Valid Values:

alarm	The log level of log event <eventID> is set to Alarm.
standard	The log level of the <eventID> log event is set to Standard.
interaction	The log level of the <eventID> log event is set to Interaction.
trace	The log level of the <eventID> log event is set to Trace.
debug	The log level of the <eventID> log event is set to Debug.
none	The <eventID> log event is not recorded in a log.

Changes Take Effect: Immediately

Specifies a log level for the <eventID> log event that is different than its default level, or disables the <eventID> log event completely. If no value is specified, the log event retains its default level. This option is useful when you want to customize the log level for selected log events. These options can be deactivated using the level-reassign-disable option.

Warning:

• Use caution when making these changes in a production environment.
• Depending on the log configuration, changing the log level to a higher priority may cause the log event to be logged more often or to a greater number of outputs. This could affect system performance.
• Likewise, changing the log level to a lower priority may cause the log event to be not logged at all, or to be not logged to specific outputs, thereby losing important information. The same applies to any alarms associated with that log event.

Notes: In addition to the preceding warnings, take note of the following:

• Logs can be customized only by release 7.6 or later applications.
• When the log level of a log event is changed to any level except none, it is subject to the other settings in the [log] section at its new level. If set to none, it is not logged and is therefore not subject to any log configuration.
• Using this feature to change the log level of a log changes only its priority; it does not change how that log is treated by the system. For example, increasing the priority of a log to Alarm level does not mean that an alarm will be associated with it.
• Each application in a High Availability (HA) pair can define its own unique set of log customizations, but the two sets are not synchronized with each other. This can result in different log behavior depending on which application is currently in primary mode.
• This feature is not the same as a similar feature in Universal Routing Server (URS) release 7.2 or later. In this Framework feature, the priority of log events are customized. In the URS feature, the priority of debug messages only are customized. Refer to the Universal Routing Reference Manual for more information about the URS feature.
• You cannot customize any log event that is not in the unified log record format. Log events of the Alarm, Standard, Interaction, and Trace levels feature the same unified log record format.

Example:

This is an example of using customized log level settings, subject to the following log configuration:
[log]
verbose=interaction
all=stderr
interaction=log_file
standard=network

Before the log levels of the log are changed:

• Log event 1020, with default level standard, is output to stderr and log_file, and sent to Message Server.
• Log event 2020, with default level standard, is output to stderr and log_file, and sent to Message Server.
• Log event 3020, with default level trace, is output to stderr.
• Log event 4020, with default level debug, is output to stderr.

Extended log configuration section:
[log-extended]
level-reassign-1020=none
level-reassign-2020=interaction
level-reassign-3020=interaction
level-reassign-4020=standard

After the log levels are changed:

• Log event 1020 is disabled and not logged.
• Log event 2020 is output to stderr and log_file.
• Log event 3020 is output to stderr and log_file.
• Log event 4020 is output to stderr and log_file, and sent to Message Server.