Log management means the management of system operation logs, system debug logs, host Agent logs, and GaussDB database logs.
All user operations performed on eReplication are logged. Operations that do not affect eReplication such as viewing and searching are not logged. eReplication 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.
eReplication has restrictions on log permission of different users as follows:
Periodically dumping system operation logs deletes database records, ensuring sufficient available space of the database. Dumped operation log files are saved in the eReplication 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. eReplication 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.
Level |
Definition |
|---|---|
Danger |
Alarms and events that may interrupt services or cause device breakdown. |
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. |
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.
You can export system debug logs, system hardware configurations, and running parameters.
The GaussDB database is installed during the installation of eReplication. 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:
Linux: /opt/gs/app/data/pg_log