Navigation: Reference > Log Reference > Analyzing Logs >
This topic describes the format of and how to analyze unified gateway operation logs.
Log Format
Table 1 describes the operation log format of the unified gateway.
Table 1 Operate log
Field |
Description |
Example |
Serial No |
The sequence number of the operation log |
6 |
Result |
Operation result. The operation result has two options according to the command execution result: ϒ⁄SUCCESS ϒ⁄FAILED |
SUCCESS |
Client IpAddress |
IP address of the PC where the configuration tool is installed. |
10.166.102.152 |
Time |
Time when an operation log is generated. |
2023-10-17 17:38:48 |
Client ID |
ID of the configuration tool, which is unique. |
29 |
Operate Content |
Command initiated by the system or a system user. |
config add prefix |
UserName |
User name of the initiated command. |
admin |
CLIType |
Type of the configuration tool connected to the unified gateway, which includes CLI, Web, eSight|LMT, BMU, and CENTERSERVER. NOTE: CENTERSERVER is used for the local node or standby node to record logs of the active node's data synchronization in a centralized call management network. |
WEB |
Log Analysis
You can learn about an operation log according to its field information. The operation log example provided in Table 1 conveys the following information: A maintenance engineer logged in to the web management system as an admin user and run the config add prefix command at 2023-10-17 17:38:48, and the execution result is SUCCESS.
Parent Topic: Analyzing Logs