diff --git a/docs/en/docs/sysmonitor/sysmonitor-usage.md b/docs/en/docs/sysmonitor/sysmonitor-usage.md index a26a8c1979be20d2bf27017d7e80341ead157cec..a159c221cd42e442d20868c24ad6966212b67f04 100644 --- a/docs/en/docs/sysmonitor/sysmonitor-usage.md +++ b/docs/en/docs/sysmonitor/sysmonitor-usage.md @@ -1,7 +1,7 @@ # sysmonitor ## Introduction - + The system monitor (sysmonitor) daemon monitors exceptions that occur during OS running and records the exceptions in the system log file **/var/log/sysmonitor.log**. sysmonitor runs as a service. You can run the `systemctl start|stop|restart|reload sysmonitor` command to start, stop, restart, and reload the service. You are advised to deploy sysmonitor to locate system exceptions. ![](./figures/sysmonitor_functions.png) @@ -417,7 +417,7 @@ REPORT_COMMAND="" | RESUME | Number greater than or equal to 0, indicating the CPU usage alarm recovery threshold | No | 80 | | MONITOR_PERIOD | Monitoring period, in seconds. The value is greater than 0. | No | 60 | | STAT_PERIOD | Statistical period, in seconds. The value is greater than 0. | No | 300 | -| DOMAIN | CPU IDs in the domain, represented by decimal numbers
- CPU IDs can be enumerated and separated by commas, for exmaple, **1,2,3**. CPU IDs can be specified as a range in the formate of _X_-_Y_, for example, **0-2**. The two representations can be used together, for example, **0, 1, 2-3** or **0-1, 2-3**. Spaces or other characters are not allowed.
- Each monitoring domain has an independent configuration item. Each configuration item supports a maximum of 256 CPUs. A CPU ID must be unique in a domain and across domains.| No | None | +| DOMAIN | CPU IDs in the domain, represented by decimal numbers
- CPU IDs can be enumerated and separated by commas, for example, **1,2,3**. CPU IDs can be specified as a range in the format of _X_-_Y_, for example, **0-2**. The two representations can be used together, for example, **0, 1, 2-3** or **0-1, 2-3**. Spaces or other characters are not allowed.
- Each monitoring domain has an independent configuration item. Each configuration item supports a maximum of 256 CPUs. A CPU ID must be unique in a domain and across domains.| No | None | | REPORT_COMMAND | Command for collecting logs after the CPU usage exceeds the alarm threshold | No | None | - After modifying the configuration file for CPU monitoring, run `systemctl reload sysmonitor`. The new configuration takes effect after a monitoring period. @@ -436,7 +436,7 @@ If a global CPU usage alarm is detected or cleared and the log collection comman ```text info|sysmonitor[127]: CPU usage alarm: 91.3% -info|sysmonitor[127]: cpu monitor: execute REPORT_COMMAND[sysmoniotrcpu] sucessfully +info|sysmonitor[127]: cpu monitor: execute REPORT_COMMAND[sysmoniotrcpu] successfully info|sysmonitor[127]: CPU usage resume 70.1% ``` @@ -444,7 +444,7 @@ If a domain average CPU usage alarm is detected or cleared and the log collectio ```text info|sysmonitor[127]: CPU 1,2,3 usage alarm: 91.3% -info|sysmonitor[127]: cpu monitor: execute REPORT_COMMAND[sysmoniotrcpu] sucessfully +info|sysmonitor[127]: cpu monitor: execute REPORT_COMMAND[sysmoniotrcpu] successfully info|sysmonitor[127]: CPU 1,2,3 usage resume 70.1% ```