Checkmk werks level1 December 2022

checkmk-werks-lvl1@lists.checkmk.com

23 participants
74 discussions

Checkmk Werk 14989: Extension package: Disable right MKP after a version was changed

by Moritz Kiemer

ID: 14989 Title: Extension package: Disable right MKP after a version was changed Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This fixes the issue where sometimes a wrong package was disabled if multiple versions of the same package where enabled.

1 year, 9 months

Checkmk Werk 14987: Extension packages: Enforce semantic versioning

by Moritz Kiemer

ID: 14987 Title: Extension packages: Enforce semantic versioning Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 This Werk only affects maintainers of Checkmk <i>Extension Packages (MKP)</i>. We now enforce both in the GUI and on the commandline the use of <a href="https://semver.org">semantic versioning</a>. Previously the GUI only allowed strings consisting of dots and digits (such as <tt>"..7"</tt>). The commandline on the other hand would allow any string at all (such as <tt>"🐟semmel"</tt>). We meet in the reasonable middle, and enforce values resembling semantic versioning upon creation or modification of packages. For now, packages with any other version string will continue to work. The <a href="https://exchange.checkmk.com/">Checkmk Exchange</a> no longer accepts packages with other versioning. <b>Note:</b> Some backend operations require us to sort the packages (to install the newest). We try our best to compare all version strings as reasonable as possible, but there are limitations. For instance: <tt>v10</tt> will be considered older than <tt>v2</tt> (because the "v" prevents an interpretation as number). This change allows to implement a well-defined version comparison in the future, allowing us to move forward with features and streamlined workflows.

1 year, 9 months

Checkmk Werk 15001: Fix possibility that changes made by form dialogs were not persisted

by Ronny Bruska

ID: 15001 Title: Fix possibility that changes made by form dialogs were not persisted Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If a user saved a form dialog, it was possible, that this change was not applied correctly. This situation could happen if a user had to many browser tabs open or spent a lot of time for one configuration step on a page before saving. Background: The maximal number of transaction IDs for a user was limited to 20 before this werk. Also, the sidebar snapins "Site status", "Master control" and "Bookmarks" used a new transaction ID on each reload of the sidebar. The number of IDs per user is now increased to 30 and the mentioned sidebar snapins no longer use transaction IDs.

1 year, 9 months

Checkmk Werk 14701: automatic discovery: Fix automatic configuration update

by Sofia Colakovic

ID: 14701 Title: automatic discovery: Fix automatic configuration update Component: config Level: 1 Class: Bug fix Version: 2.2.0i1 If 'Automatically update service configuration' option in rule 'Periodic service discovery' was activated and 'Group discovery and activation' period was bigger than the discovery period, the configuration of the services would never be updated. The problem is now fixed and the service configuration is updated.

1 year, 9 months

Checkmk Werk 15071: UI: Introduce new toggle icon

by Kenneth Okoh

ID: 15071 Title: UI: Introduce new toggle icon Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 Page menu entries which toggle certain view parameters, e.g. "Show checkboxes" in the "All hosts" view, used to show a checkbox icon, that was either empty or checked. For a more intuitive, consistent and visually understandable user experience, a new toggle icon is introduced and the text of such entries is toggled accordingly.

1 year, 9 months

Checkmk Werk 15015: Add OMD disk usage check plugin

by Max Linke

ID: 15015 Title: Add OMD disk usage check plugin Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 Adds new check plugin 'omd_diskusage' to monitor the disk usage of various omd components.

1 year, 9 months

Checkmk Werk 15014: $HOSTADDRESS and $HOSTNAME can be used in aggregation names

by Max Linke

ID: 15014 Title: $HOSTADDRESS and $HOSTNAME can be used in aggregation names Component: BI Level: 1 Class: Bug fix Version: 2.2.0i1 As stated in the documentation for rule 'Check State of BI Aggregation' $HOSTADDRESS and $HOSTNAME can now be used in aggregation names.

1 year, 9 months

Checkmk Werk 14998: Remove long deprecated flexible and plain email notifications

by Ronny Bruska

ID: 14998 Title: Remove long deprecated flexible and plain email notifications Component: Notifications Level: 2 Class: New feature Version: 2.2.0i1 This change only affects you, in case you have set the global setting "Rule based notifications" to "Off" in your installation. Flexible and plain email notifications are deprecated since version 1.5. If you still use flexible or plain email notifications configured within the user profile, this werk will remove this notification option in the usersettings and the GUI. Affected users will be logged to ~/var/log/update.log, e.g.: "Removed notification configuration from user: MY_USER" All listed users will automatically be updated to use the rule based notifications. Effectively, the HTML email notifications will be enabled for them. If you want to use a different notification mechanic, then review the notification rules and update them according to your needs. You can find more about the notification configuration <a href='https://docs.checkmk.com/latest/en/notifications.html'>here</a>. Still existing spool files will be converted to HTML email notifications on update. If a remote site with a version prior 2.2 has flexible or plain email notifications enabled and uses notification forwarding, the notifications will be coverted to HTML email notifications on the recieving site.

1 year, 9 months

Checkmk Werk 15013: $HOSTADDRESS and $HOSTNAME can now be used in aggregation names

by External contributor

ID: 15013 Title: $HOSTADDRESS and $HOSTNAME can now be used in aggregation names Component: BI Level: 1 Class: Bug fix Version: 2.2.0i1 As stated in the inline help $HOSTADDRESS and $HOSTNAME can now be used in aggregation names.

1 year, 9 months

Checkmk Werk 15002: Fix "Base on role" default while cloning roles

by Ronny Bruska

ID: 15002 Title: Fix "Base on role" default while cloning roles Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If you cloned a rule multiple times, from the second clone on, the "Based on role" property had the default "Administrator", no matter what initial builtin role was cloned. The property will now always show the builtin role of the source role that was cloned. E.g. if you clone "guest" multiple times, the clones will always show "Guest user".

1 year, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2022