How-to monitor the site processes
Monitoring the Checkmk site's processes, like CMC and helpers, is useful for debugging performance issues, spotting memory leaks, and responding quickly to outages or missed notifications.
LAST TESTED ON CHECKMK 2.3.0P1
This article applies to Checkmk versions up to 2.3.0pX. Starting with Checkmk 2.4.0, this information is no longer relevant and can be safely ignored for newer versions, as there is now a built-in process monitoring.
Those manually created rules up to 2.3.0pX won't be removed automatically when upgrading to 2.4.0 and have to be removed manually.
Also, it's recommended to remove these process discovery rules, as this will only cause confusion with the built-in process discovery rules. Please make sure to update all other places in the Setup menu wherever those process names are being referred.
Step-by-step guide
To configure all relevant site processes to be monitored, follow these steps:
Create a Process discovery rule:
.
After saving and activating the changes, do a service discovery on your Checkmk server hosts. There, you will see a bunch of services to be added:
.
Some of these processes should only run once, so let's add a "State and count of processes" rule for them:
Alternative regular expressions for monitoring particular Site processes
We recommend monitoring all site processes, but if you want to pick particular sets of processes, you can use these regular expressions:
Component | Regular Expression |
|---|---|
Active check helpers |
|
Agent receiver |
|
Alert handler |
|
Checkers |
|
DCD | (dcd) |
Event console |
|
Fetchers |
|
ICMP receiver |
|
ICMP sender |
|
Liveproxy daemon | (liveproxyd) |
Microcore |
|
Notification helpers |
|
Notification spooler |
|
RRD cache daemon |
|
RRD helpers |
|
Real-time helper |
|
Redis DB |
|
Site Apache | \/usr\/sbin\/apache2 -f \/omd\/sites\/\w+\/etc\/(apache)\/apache.conf |
Each of these expressions contain one group, so you can use "%u/%1" as Process name in your Process discovery rule.