TMS zl Management and Configuration Guide ST.1.1.100430

2-76
Initial Setup in Routing Mode
Configure Event Logging
Log Severity
The TMS zl Module automatically classifies events according to severity.
Event severity levels are listed below from most severe to least severe:
■ Critical
■ Major
■ Minor
■ Warning
■ Information
By default, the event severity is set to Critical, meaning that only critical
messages are logged. When troubleshooting a problem or monitoring your
TMS zl Module, you may want to change the severity level so that the TMS zl
Module logs more events. The less severe the setting level, the more events
the TMS zl Module logs.
For example, when troubleshooting a problem, you may want to set the
severity level to information so that the TMS zl Module logs a message for
nearly all TMS zl Module events. Keep in mind, however, that logging events
requires processor time. Each time you select a less severe setting, the TMS
zl Module must devote more time to logging messages. The information setting
is particularly processor-intensive and could degrade the module’s perfor-
mance. As soon as you complete your troubleshooting, you should return the
severity level to its default setting of critical.
Log Threshold Monitor
You can select the Enable log threshold monitoring option to help prevent
excessive logging from negatively impacting the TMS zl Module’s perfor-
mance. When enabled, this feature evaluates the logging engine’s resource
consumption. If the resource consumption becomes high enough to negatively
impact the performance of the module, the log severity threshold will be reset
to Critical.
Unusually high resource utilization may be caused by abnormal network
events, but it can be exacerbated by a lower log severity threshold (such as
Minor or lower). Selecting the Enable log threshold monitoring option will
prevent excessive logging from negatively impacting the TMS zl Module’s
performance: if such an event occurs, it will result in only Critical level logs
being generated. If other events are negatively impacting the module’s perfor-
mance, you will need to investigate and monitor those events separately.