[Release] Checkmk stable release 2.3.0p20

Announcements
, , ,
1

Dear friends of Checkmk,

the new stable release 2.3.0p20 of Checkmk is ready for download.

This stable release ships with 13 changes affecting all editions of Checkmk,
2 changes for the Enterprise editions, 0 Cloud Edition specific and
0 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

Checks & agents

  • 16899 oracle_locks: allow checking w/o setting a state…
  • 17209 FIX: if64: Use Uptime instead of Check Time…
  • 17323 FIX: Azure agent: fix query for backend IP configurations in virtual machine scale set…
  • 17196 FIX: Crash in during HW/SW inventory on Windows…
  • 17040 FIX: agent_netapp_ontap: KeyError: ‘used’…
  • 17211 FIX: dell_powerconnect_cpu: Fix KeyError…
  • 17380 FIX: mknotifyd: Wrong service descriptions…

Other components

  • 17332 FIX: Fix pushed MKPs in distributed monitoring being impossible to disable…

Setup

  • 17334 FIX: Catch invalid “Explicit hosts” condition on save instead of crashing…
  • 17333 FIX: Stop dropdowns in form groups from breaking scroll behavior…

Site management

  • 17212 Extend Site Apache CustomLog LogFormat…

User interface

  • 17391 FIX: Dashboards and graph collections: Fix “There is no graph template with the id ‘commit_charge’”…
  • 17356 FIX: Decode semi-colon from monitoring history…

Changes in the Checkmk Enterprise Edition:

Checks & agents

  • 17309 FIX: checkmk_agent: Respect “State if agent deployment is disabled for host” setting…

Metrics system

  • 17390 FIX: Fix update of graph collections with combined graphs…

Changes in the Checkmk Cloud Edition:

NO CHANGES

Changes in the Checkmk Saas Edition:

NO CHANGES

Changes in the Checkmk Managed Services Edition:

NO CHANGES

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

List of all changes: Werks

We greatly thank you for using Checkmk and wish you a successful monitoring,

Your Checkmk Team

2

We still are experiencing extreme slowness. We have gone from 6 cpus (2.2) to 12 cpus (2.3), but that didn’t help. We are worse off now with 12 cpus than when running 2.2 on 6 cpus.

3

@eplpaho while we see (and documented) a slight increase in resource utilization witch Checkmk 2.3.0, what you describe cannot be an effect of the software update alone. I recommend you open a dedicated post, sharing some more background or if possible open a support ticket, so the matter can be better approached.

4

Exactly, the same issue. It is so much lagging after upgrading to 2.3 even the increase in CPU and memory is not helping much.

5

Having similair experience on 2.3.0p18. It was laggy and would sometimes kick the CPU to a 100% and kept going there.
Now we have upgraded the machine from 2vcpu / 8GB to 4vcpu / 16 GB, which makes it run more smoothly.

We’re running a distributed setup, so that might be part of the reason it needed more resources… But since we never had issues in 2.2 the needed increase seems strange.

Happy to share some more information in private if that helps locating possible issues.