Page Comparison

...

Adjust the helper settings

In any case If you need decide to adjust the helper settings, please be aware of these settingsettings:

Setup → General → Global Settings → Monitoring Core →

• Maximum concurrent active checks

  increase the helper for the active checks

  Note
  The usage should stay under 80% on average.

  
  

• Maximum concurrent Checkmk fetchers

  increase the helper for the Checkmk fetchers

  Note
  With increasing 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

  increase the helper for the 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.

  
  

• Maximum concurrent Livestatus connections

...

Please see this manual to check the Livestatus PerfomancePerformance

Required log files

Please see this manual to enable debug log of the helpers. The required settings are:

...

1. fetcher helper usage is permanently above 96% and fetcher count is already high (i.e., >50 or 100 or more) and
2. the service "Check_MK" runs into constant "CRIT with fetcher timeouts   

This is a strong indicator that you might have plugins/local checks (primarily in Windows) that have a quite a long runtime.

Increasing the fetcher helper further here is not constructive. Instead, you have to identify the long-running plugins/local checks and set them to asynchronous execution and/or define a (generous) cache settings or even timeouts especially for them.

...