Event Recording

Overview

• Logging: The system generates detailed operation logs. The log files are stored in the following paths:
  • Windows: C:\MgC-Agent\logs\audit\audit.log
  • Linux: /opt/cloud/MgC-Agent/logs/audit/audit.log
• Event recording: On the MgC Agent console, you can view event records, which include event details such as the event source, involved resources, key behaviors, operation time, and operation result.
• Filtering and search: You can filter event records by key behavior or search for event records by keyword.
• Troubleshooting: If an operation fails, you can review the logs to learn what the cause is.
• Key operation and resource display:
  • For key actions such as changing passwords or credentials, the resource field displays the involved account name or credential ID.
  • For key actions such as MgC delivering instructions to the MgC Agent or the MgC Agent reporting data to MgC, the resource field displays the path of the file that stores the instructions or data. You can find the file using the following path:
    • Instructions delivered from MgC are stored in the downlink_command.txt file. The file path is as follows:
      • Windows: C:\MgC-Agent\logs\audit\downlink_command.txt
      • Linux: /opt/cloud/MgC-Agent/logs/audit/downlink_command.txt
    • Data reported to MgC is stored in the uplink_data.txt file. The file path is as follows:
      • Windows: C:\MgC-Agent\logs\audit\uplink_data.txt
      • Linux: /opt/cloud/MgC-Agent/logs/audit/uplink_data.txt
• Periodic log archiving: The system automatically compresses the audit.log file into a .zip package at the beginning of each month and saves the package to the /audit/ directory. The package name is in the format of year-month.zip, for example, 2024-xx.zip. The directory path is as follows:
  • Windows: C:\MgC-Agent\logs\audit\
  • Linux: /opt/cloud/MgC-Agent/logs/audit/