CheckMk Timers
Lets start adjusting our Timers. Checkmk normally checking for services every minute. This leads to high Network traffic and CPU load on the checkmk machine. For this reason we want to lower our checkmk timers.
In you're checkmk instance go to setup > Service monitoring rules > Normal check interval for service checks. Click on add to create a new rule and adjust you're settings as you wish i chose every 10m and set Host tags to Monitoring agents / Monitoring via Checkmk Agent.
Save the rule.
Lets move on and set the rule setup > Service monitoring rules > Retry check interval for service checks > add Rule
Create the rule and save it. Than click on the exclamation mark on the top right and click activate on selected sides.
Now check if the rule is applied: Monitor > all hosts > select a host > select a service and search for Service normal/retry check interval it now should look something like this:
I just used this setting for my checkmk test environment. In a productive company network, waiting time of 5 minutes for normal check intervals and retry check intervals of 1 to 2 minutes are recommended.
If you're not going to monitor containers you can end here.
As I start monitoring docker containers in my next article we need to define rules for piggyback data. In Check_MK, piggyback data refers to monitoring data collected from one host but attributed to another.
SetupServices > Service monitoring rules > Normal check interval for service checks > addRule
I choose here 30 min as i want to rely lower my CPU Usage of the Server. Change Host tags Monitoring agents / Piggyback and save.
Now continue and move to SetupServices > Service monitoring rules > Retry check interval for service checks > addRule
I choose here 1 day because if containers going offline there is no need of rechecking. But adjust these settings as you need, but remember a lot of Piggyback checking results in High CPU loads.
Click the exclamation mark on the top right and > select on activated sites.
You're done. Happy monitoring 😃 .