os_mon.cpu_check_interval | duration | 60s | Check interval for CPU usage |
os_mon.cpu_high_watermark | percent | 80% | The high watermark of the CPU usage, which is the threshold to activate the alarm |
os_mon.cpu_low_watermark | percent | 60% | The low watermark of the CPU usage, which is the threshold to deactivate the alarm |
os_mon.mem_check_interval | duration | 60% | Check interval for memory usage |
os_mon.sysmem_high_watermark | percent | 70% | The high water mark of the system memory usage. The alarm is activated when the total memory occupied by the application reaches this value |
os_mon.procmem_high_watermark | percent | 5% | The high water mark of the process memory usage. The alarm will be activated when the memory occupied by a single process reaches this value. |
vm_mon.check_interval | duration | 30s | Check interval for the number of processes |
vm_mon.process_high_watermark | percent | 80% | The high watermark of the process occupancy rate, that is, the alarm is activated when the ratio of the number of created processes to the maximum number limit reaches this value |
vm_mon.process_low_watermark | percent | 60% | The low water mark of the process occupancy rate, that is, the alarm is deactivated when the ratio of the number of created processes to the maximum number limit drops to this value |
alarm.actions | string | log,publish | The action triggered when the alarm is activated, and it currently only supports log and publish, which is to output log and publish system messages |
alarm.size_limit | integer | 1000 | The maximum number of saved alarms that has been deactivated. After the limit is reached, these alarms will be cleared according to the FIFO principle |
alarm.validity_period | duration | 24h | The maximum storage time of deactivated alarms, and expired alarms will be cleared |