[Release] Checkmk stable release 2.4.0p15

[Checkmk-Announcement (Checkmk Announcements)]

Dear friends of Checkmk,

the new stable release 2.4.0p15 of Checkmk is ready for download.

This stable release ships with 15 changes affecting all editions of Checkmk,
4 changes for the Enterprise editions, 3 Cloud Edition specific and
1 Managed Services Edition specific changes.

Changes in all Checkmk Editions:

Checks & agents

• 17999 SEC: Update Python runtime for Windows Agent…
• 18694 FIX: mk_job: use environment MK_VARDIR value if set…
  NOTE: Please refer to the migration notes!
• 18696 FIX: netapp_ontap_interfaces: correctly monitor interface state…
  NOTE: Please refer to the migration notes!
• 18594 FIX: Properly remove extension packages containing EC rule packs…
• 18302 FIX: diskstat: Support devices without WWN for virtual disks…
• 18478 FIX: ibm_storage_ts_drive: handle empty string for read/write errors…
• 18695 FIX: mk-job: Allow non-root users to create output directories…
• 18693 FIX: netapp_ontap_interfaces: remove physical interface grouping…

Event console

• 18644 FIX: Fixed Regex Based Filters for Event Console…
• 17756 FIX: Improved SQLite housekeeping for event console history…

Notifications

• 18927 FIX: Notifications: handle undefined mail variables…

Reporting & availability

• 18952 FIX: Fix crash rendering availability timeline…

Setup

• 18138 FIX: Fix multiple-select field rendering in Chrome version 142+…

Site management

• 18160 FIX: omd update: Add --conflict=ignore…
• 18882 FIX: omd update: Fix --conflict=abort behaviour…

Changes in the Checkmk Enterprise Edition:

Agent Bakery

• 18917 FIX: Agent updater/non-root agent: Stops working after logfile rotation…
  NOTE: Please refer to the migration notes!
• 18609 FIX: MS Office checks: Microsoft Graph PowerShell module must be installed manually…
  NOTE: Please refer to the migration notes!
• 18098 FIX: Agent baking is now triggered when upgrading from Raw to Enterprise Edition…

BI

• 18953 FIX: Fix crash when viewing BI aggregation…

Changes in the Checkmk Cloud Edition:

Checks & agents

• 18314 OTel: Make collector memory limit configuration available in global settings…
• 18313 FIX: OTel: Sanitize curly braces from metric name…
• 18311 FIX: OTel: Use site certificates for TLS encryption…

Changes in the Checkmk Cloud (SaaS):

NO CHANGES

Changes in the Checkmk Managed Services Edition:

Ntopng integration

• 18620 FIX: MSP: missing ntopng username field for site-specific ntopng configuration…

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

[Holger (Holger Eudenbach)]

Got Broken Notifications after update but got them fixed:

Hi, we are using customised Notification Scripts for OpsGenie/Jira - after the Update from 2.4.0p13 to 2.4.0p15 (skipped p14 due to the BI Break) we observed, that no more OpsGenie Calls or Tickets in Jira are triggered, after some debugging we found, that in the Notification Rules the Select Parameters field was filled, but if you clicked on Edit the Fields where all empty

after we toggled the Parameters Field with an other rule, and back to the right one the Fields under Edit where filled again and the Rule did work again.

We found this after browsing the ~/var/log/notify.log and stumbled upon this error - which lead to the assumption that something in the Notification Rules is missing or wrong.

[gstolz (Gerd Stolz)]

@Holger my colleague @mhoess has reproduced this and it has been confirmed by Checkmk support and handed over to their Dev team Problem with Notification-Rule-Conversion when upgrading from CMK 2.3 -> 2.4p15

[LaSoe (Lars Sörensen)]

Is there already an official statement from Checkmk regarding who might be affected by this issue? Does it affect only customised Notifications that use the Parameters Field or notifications in generall?

We have around 550 notification rules, so it would be helpful to know that bevor we go for 2.4.0p15.

[martin.hirschvogel]

See the thread (for the issue mentioned by gstolz). Looks like a singular problem with old notification configuration from 1.6, but we will continue to look into it.

Added: We also look into Holger’s issue and have reached out to him.

[foobar]

Werk #18859: HTML email: Migrate old ‘From’ format

[_rb]

@foobar

Werk #18859: HTML email: Migrate old ‘From’ format

This is the fix for the problem mentioned in this thread:

Problem with Notification-Rule-Conversion when upgrading from CMK 2.3 -> 2.4p15

Hi, JFI: We experienced in 2 instances, that coming from CMK 2.3 that notification-rules weren’t properly converted (the notification-plugin-params got lost, messages from cmk-update-config for that appeared in the update.log ). We contacted support, which could reproduce the problem and informed the Devs to fix. So probably best to keep a copy of your notifications.mk or to make some screenshots before doing an upgrade/update, currently Micha

Investigation on this is still ongoing:

[Release] Checkmk stable release 2.4.0p15

Got Broken Notifications after update but got them fixed: Hi, we are using customised Notification Scripts for OpsGenie/Jira - after the Update from 2.4.0p13 to 2.4.0p15 (skipped p14 due to the BI Break) we observed, that no more OpsGenie Calls or Tickets in Jira are triggered, after some debugging we found, that in the Notification Rules the Select Parameters field was filled, but if you clicked on Edit the Fields where all empty [image] after we toggled the Parameters Field with an other r…

We could not reproduce the issue yet and @Gav is waiting for an answer from @Holger to get more details.