[Release] Checkmk stable release 2.1.0p21

Dear friends of Checkmk,

the new stable release 2.1.0p21 of Checkmk is ready for download.

This maintenance release ships with 29 changes affecting all editions of Checkmk,
8 Enterprise Edition specific changes and 0 Managed Services Edition specific changes.

Support periods can be found here: Checkmk versions

Changes in all Checkmk Editions:

Agent bakery:

  • 13444 FIX: mk_mongodb.py: Improve performance for replication info
  • 15271 FIX: solaris agent did not report zpool status

Checks & agents:

  • 15115 More detailed output of the ā€œmkp listā€ commandā€¦
    NOTE: Please refer to the migration notes!
  • 15233 FIX: Discovery: Improve performance and prevent apache timeoutā€¦
  • 15019 FIX: Fix proxmox agent crash with shutdown nodesā€¦
  • 15235 FIX: Missing agent sections in rare upgrade scenarioā€¦
  • 15234 FIX: Periodic service discovery: Vanished clustered services can now be removed automaticallyā€¦
  • 15262 FIX: mk_postgres.py: Improved instance process detection
  • 14970 FIX: mk_postgres.py: Use PATH as fallback for psql binary locationā€¦

Event console:

  • 14724 Improve EC performance when processing large logwatch.ec spool filesā€¦

HW/SW inventory:

  • 15093 FIX: HW/SW Inventory history: Fix missing row fields if changed

Metrics system:

  • 14940 FIX: Fix hex to rgb color conversionā€¦


  • 13445 FIX: Allow single character namesā€¦
  • 15381 FIX: Host Tag can now be ā€œnullā€ in REST API responses
  • 15217 FIX: custom_user_attributes: after deleting, all user config will be updatedā€¦
  • 15209 FIX: host_config: fix host attribute IPv6 address validationā€¦
  • 15212 FIX: host_tag_groups: allow nullable on tag group choice identā€¦
  • 15371 FIX: rest-api: alias field now required when creating a contact group
  • 15372 FIX: rest-api: alias field now required when creating a host group
  • 15214 FIX: rest_api: aux_tag creation/updating could set the title to Noneā€¦
  • 15213 FIX: rest_api: time_period exception/active time_ranges defaultā€¦
  • 15218 FIX: time_period: response schemas updated to align with other endpointsā€¦
  • 15215 FIX: user_config: Error when creating a user with an idle timeout duration via the rest-apiā€¦
  • 13443 FIX: list rules endpoint failed to list rulesets containing a hyphenā€¦
    NOTE: Please refer to the migration notes!


  • 14180 Improved performance when processing clusters and cluster rules
  • 15187 FIX: Enforce password policy in REST API and user managementā€¦
  • 14181 FIX: Improved speed of cmk-update-config which runs during software update

Site management:

  • 14792 FIX: Enable pip install of packages as site userā€¦

User interface:

  • 15124 FIX: Fix KeyError on usage of filter ā€˜Host has software packageā€™

Changes in the Checkmk Enterprise Edition:

Checks & agents:

  • 14963 Check_MK Agent service: State if host is exluded from agent updatesā€¦

Core & setup:

  • 15156 Send metrics to InfluxDB in batchā€¦
  • 15157 Zip metrics sent to InfluxDBā€¦
  • 15252 FIX: Fixed ā€œprocessing of perfdataā€ conditionā€¦
  • 15158 FIX: Restart periodic notifications after FLAPPINGSTOP

Dynamic host configuration:

  • 14580 FIX: DCD: Piggyback hosts are now updated and deleted again
  • 15170 FIX: DCD: fix REST API authentication problemsā€¦


  • 15208 users: fix error when changing the password for an existing userā€¦

Changes in the Checkmk Managed Services Edition:


You can download Checkmk from our download page: Download Checkmk for free | Checkmk

List of all changes: Werks

Please mail bug reports and qualified feedback to feedback@checkmk.com.
We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team


Is cmk-update-config the same like activate changes in the GUI? If yes then we donā€™t got any performance improvements.
Would be nice if there is a solution for that finally because each activation took very long.

No, this is only called during the site update process. Today i updated some sites to p21 and i can say it is way faster than before the updates to p19 or p20.

I have no problems with long activation times. How big is your biggest single instance?

1 Like

@andreas-doehler Do you mean checkmk instance or monitored instance? And what you mean by how big?

There was already a thread where the activation was discussed and an excessive usage of pw-store was the case. But it still takes 35 seconds and that is too long.
But as that is not related to the Werk I will open another thread and we donā€™t need to discuss here.

it was only during updates.
We had site updates running for nearly 20min! Luckily Andreas (tribe29) took care of it and fixed it.

Auf den ersten Blick kann man von den 1080 Sekunden mit einem einfachen Fix bestimmt 992 Sekunden einsparen

Supposed to be normal speed again

Ah ok sounds great! We didnā€™t face that yet luckily. But yeah I was wrong here and I was hoping that this fix was improving the ā€œactivation of changesā€ which is slow too.

yes fully agree, still taking a lot of time and it became slower with 2.0 for us - even if nobody is believing us :wink:
2.0 = ā€œEntschleunigungā€
But with 2.2 everything will become better