Appendix - Modular MCU
Polycom, Inc. 368
● All logging operations use the same infrastructure elements, thus are consistent across the MMCU
various components.
Logs Format
In all Soft Blades, logs are formated as
D:<Date and time stamp> E:<Entity> P:<Process> U:<Unit> L:<Log level> SN:<#>
Lcnt:<code location>
where:
Logs generated with ERROR/FATAL logging level are immediately sent to the Logger of the TC at the Main
MCU as faults, as well as logged on the Soft Blade.
Logging Configuration
All logging performed at the Soft Blades, share the same configuration, especially their logging level, and
are configurable via the Main MCU, although the Main MCU may use different logging configuration.
Nevertheless, the system initial state, is that of the Main MCU sharing its default logging configuration
(INFO) with the Soft Blades.
In normal situations, INFO is the logging level. To obtain detailed logs, logging level at both the Main MCU
and the Soft Blades should be set to TRACE/DEBUG.
Logging volume varies according to the logging level. However, it is designed so that, assuming a total of
15GB storage, approximately one month worth of logs can be stored.
To determine the configuration settings for the Soft Blades:
1 In the Collaboration Server main menu, select Administration > Tools > Logger Configuration.
Log Component Description and structure
Date and time stamp Date and time of log generation, in the format dd/mm/yy-hh:mm:ss.ms
Entity System entity generating the log
Process Soft Blade application process generating the log
Unit Unit generating the log
Log level Logging level at the point of log generation. One of:
• TRACE
• DEBUG
• INFO (default)
• WARN
• ERROR
• FATAL
# Log message serial number
Code location Code file name, and line number
To Next Page
Loading...
