| Info |
|---|
The following article explains how to monitor and adjust the performance in Checkmk. |
Table of Contents
First, there is no difference in the requirements for the virtual and hardware appliances.
...
The only overview regarding needed resources we have is, and it is just a rough approximation: https://checkmk.com/product/appliances
We always recommend customers to orientate on the specifications for the HW Appliance.
When importing the virtual appliance, we have some default values preconfigured. Please check out this page: https://docs.checkmk.com/latest/en/introduction_virt1.html#_import_the_appliance
As this is a virtual machine, you can adjust these values anytime.
Table of Contents
Configuration of Fetcher/Checker settings
...
- PDF report with graphs of
- CPU
- Memory
- OMD <SITENAME> Performance
- activate the "Core statistics" snap in
- Check_MK
- Disk I/O Summary
- The local structure
- find -L ~/local > local.txt (as site user)
...
Setup → General → Global Settings → Monitoring Core →
- Maximum concurrent active checks note
- The usage should stay under 80% on average.
- The usage should stay under 80% on average.
Maximum concurrent Checkmk fetchers
note- With increasing the number of fetchers, your RAM usage will rise, so make sure to adjust this setting carefully and keep an eye on the memory consumption of your server.
- The usage should stay under 80% on average.
Maximum concurrent Checkmk checkers
Note - The number of checkers should not be higher than your CPU core count! If you have more than two cores, the rule of thumb is:
Maximum checkers = number of cores - 1. - The usage should stay under 80% on average.
- The number of checkers should not be higher than your CPU core count! If you have more than two cores, the rule of thumb is:
- Maximum concurrent Livestatus connections
...
- In a distributed monitoring setup, having different values for the remote sites may be helpful. You will find the guidance on how to do that here!
Check the Livestatus Performance
...