Introduction to Log Management

Log management means the management of system operation logs, system debug logs, and GaussDB database logs.

System Operation Logs

All user operations performed on UltraVR are logged. Operations that do not affect UltraVR such as viewing and searching are not logged. UltraVR provides the function of browsing operation logs and filtering logs by log level, administrator, log category, operation results, as well as log start time and end time. Logs also help you understand user operations. For example, you can view the operations that are performed by a user on the NMS.

UltraVR has restrictions on log permission of different users as follows:

Super administrators have all permissions.
Common administrators granted the viewing permission can view their own operation logs only.
Administrators without permission cannot view any operation log.

Periodically dumping system operation logs deletes database records, ensuring sufficient available space of the database. Dumped operation log files are saved in the UltraVR Sever installation directory//Runtime/LegoRuntime/datastorage/sysoptlog path. A user can download the dumped system operation files on the client and delete unnecessary log files under the directory.

Operation log levels indicate the severity of the log. UltraVR classifies system operation logs into three levels: Warning, Minor, and Info from the most critical to the least critical. Table 1 defines different levels of system operation logs.

**Table 1** Log levels
Level	Definition
Warning	Operations that may cause data inconsistency of the entire system or a function module, for example, Delete Recovery Plan.
Minor	Normal operations on a system or function module, for example, Deliver refreshing resource command.
Info	Operations, which impact no service running, on a system or function module, for example, Deliver a protected group creation command.

System Debug Logs

Debug logs record the software running status that cannot be detected by the system, such as the object status change and record of an abnormal message. Debug logs help system maintenance personnel locate faults and analyze the system running efficiency.

System debug log levels indicate the severity and importance of logs. UltraVR classifies system debug logs into four levels: Error, Warning, Info, and Debug from the most critical to the least critical. Table 2 defines different levels of system debug logs.

**Table 2** Levels of system debug logs
Level	Definition
Error	Errors occurred during system running, such as file damage, which may lead to abnormalities of some functions and recovers only after manual intervention.
Warning	Information about foreseeable and processable local abnormalities, such as processing timeout.
Info	Software running tracks. Such logs records the information about function invocation.
Debug	Debugging information that is provided to the R&D personnel.

GaussDB Database Logs

The GaussDB database is installed during the installation of UltraVR. Run logs and debug logs generated during the running process of the GaussDB database are called system logs. Run logs are generated during the normal running of the database. Debug logs are generated when a database application is being developed and commissioned. During the running of the GaussDB database, a large volume of run logs are generated, consuming large disk space. You are advised to retain run logs generated only in the latest one month.

The aussDB database logs are saved the following path: /opt/gs/app/data/pg_log