The UX logging service allows you to troubleshoot issues such as call signaling, call quality and performance by collecting activity logs from its subsystems. These logging records can then be analyzed to diagnose problems and optimize the performance of UX for your environment.
The UX system supports the following methods for recording logs:
- Remote Syslog configuration, uses a syslog server to store a larger amount of log activity for extended period of time. Using a Remote Logging configuration is the recommended logging method since it allows for a greater logging history and level of detail. You must use this method of logging when working with NET customer support.
- Local Log (available only on the UX2000 chassis model) configuration, stores temporary log files directly on the UX system. Each local log file retains a limited amount of recorded log messages. Local logging is only useful for quick, high level, troubleshooting, and is not recommended (nor suited) for extended troubleshooting sessions.
A fully running UX system can generate a large amount of logging information. For this reason, the UX logging service allows you to customize the types of logging messages (and level of detail) you wish to be recorded by Managing Subsystems Logging.