Jump to: navigation, search


This section is defined on the Options tab of the Stat Server Application object and has to be named log-extended.



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 and keep the customizations.


Default Value: Default value of log event <eventID>. Refer to the Common Log Events Help or statserver.lms (located in the directory where Stat Server is installed) for a listing of each of Stat Server’s the default levels.

Valid Values:

  • alarm The log level of log event <eventID> is set to alarm.
  • standard The log level of log event <eventID> is set to standard.
  • interaction The log level of log event <eventID> is set to interaction.
  • trace The log level of log event <eventID> is set to trace.
  • debug The log level of log event <eventID> is set to debug.
  • none Log event <eventID> is not recorded in a log.

Changes Take Effect: Immediately
Related Options: level-reassign-disable

Specifies one of five log levels for log event <eventID>, which may differ from its default level, or disables logging of the named event altogether. This option is useful if you want to change the behavior of what Stat Server logs for the specified log event ID. If no value is specified, then the named log event retains its default level.

You can deactivate these options with the level-reassign-disable configuration option.

Use caution when making these changes in a production environment.

Depending on the log configuration, changing the log level to a higher priority might 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 not logged to specific outputs, thereby losing important information. The same applies to any alarms associated with that log event.

In addition to the precautionary message above, 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 therefore not subject to any log configuration.
  • Changing the log level of a log using this feature 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, version 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 Server Reference Manual, available on the Universal Routing page, 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.


This is an example of using customized log level settings, subject to the following log configuration:


Before the log levels of the log are changed:

  • Log event 20009—with default level trace—is output to stderr.
  • Log event 20018—with default level standard—is output to stderr and the log file, and sent to Message Server.
  • Log event 20022—with default level debug—is output to stderr.

Extended log configuration section:


After the log levels are changed:

  • Log event 20009 is disabled and is not logged.
  • Log event 20018 is output to stderr and to the log file.
  • Log event 20022 is output to stderr and to the log file, and sent to Message erver.
This page was last edited on July 22, 2015, at 15:32.


Comment on this article:

blog comments powered by Disqus