ID: 15754
Title: Enable AES-192 and AES-256 privacy protocols for SNMP
Component: inline-snmp
Level: 2
Class: New feature
Version: 2.3.0b1
This werk enables the AES-192 and AES-256 privacy protocols
to be used in SNMP monitoring.
ID: 15493
Title: Adjustments to local extensions may be required
Component: Multisite
Level: 2
Class: New feature
Version: 2.2.0
In 2.2, we moved a lot of internal UI code and removed implicitly imported
names to reduce unclear situations. This helps our internal code structure, but
may cause issues for existing extensions which were relying on these moved or
removed names.<br><br>
It is important to note that such code restructuring is part of the continuous
improvement and evolution of Checkmk. These changes can lead to more efficient
workflows, improved features, and better performance.<br><br>
For 2.2 we tried to keep compatibility for the most extensions but could not
make sure to cover them all.<br><br>
Therefore, we would like to give you a few examples, how to adjust local
extensions if you see incompatibilities with Checkmk 2.2.<br>
Please note: Each example stands for one possible import problem, so the module
names are interchangeable.<br><br>
<b>Loading "metrics/my_custom_file" failed: No module named
'cmk.gui.plugins.metrics.check_mk'</b><br>
There is an import from the not existing module "cmk.gui.plugins.metrics.check_mk".
Check your plugin to see what is imported from there, e.g. "df_translation" and
add the import:
F+:metrics/my_custom_file
from cmk.gui.plugins.metrics.translation import df_translation
F-:
<b>Loading "views/my_custom_file" failed: name 'inventory_displayhints' is not
defined</b><br>
In earlier versions, an explicit import was not needed, with 2.2 you have to
add:
F+:views/my_custom_file
from cmk.gui.views.inventory.registry import inventory_displayhints
F-:
<b>Loading "wato/my_custom_file" failed: cannot import name
'RulespecGroupIntegrateOtherServices' from
'cmk.gui.plugins.wato.active_checks'</b><br>
The location of some modules may have changed. The simplest way to find the new
place is to grep for it in '~/lib/python3/cmk/gui' and adjust the import in
bar:
F+:wato/my_custom_file
from cmk.gui.plugins.wato.active_checks.common import RulespecGroupIntegrateOtherServices
F-:
<b>Loading "wato/my_custom_file" failed: name 'socket' is not defined</b><br>
System modules like 'socket' have to be imported from 2.2 on, so please add:
F+:wato/my_custom_file
import socket
F-:
For Checkmk 2.3 we plan to introduce a fully described API to avoid such
adjustments with every major release in the future.<br><br>
Also see related werks:
<a href='https://checkmk.com/werk/13094'>Werk #13094: Various ValueSpec-related API cleanups</a>
Dear Checkmk users,
this mailinglist will now be migrated to a new server on lists.checkmk.com.
Let's say farewell to the last mathias-kettner.de server.
--
Alexander Wilms
Head of IT
Checkmk - The IT monitoring platform | checkmk.com <https://www.checkmk.com>
alex.wilms(a)checkmk.com | Phone: +49 89 9982097 0
Subscribe to our newsletter <https://go.checkmk.com/newsletter>! | Melden
Sie sich bei unserem Newsletter <https://go.checkmk.com/de/newsletter> an!
Checkmk GmbH
Kellerstraße 27, 81667 München, Germany
Amtsgericht München, HRB 165902
Geschäftsführer: Jan Justus, Mathias Kettner
ID: 15611
Title: Migrate <tt>Locked by</tt> during site renamings
Component: Site Management
Level: 2
Class: Bug fix
Version: 2.2.0b7
Users which execute <tt>omd mv</tt> or <tt>omd cp</tt> expect Checkmk to not only rename the site,
but also migrate the existing configurations created by the <tt>Dynamic host management</tt>.
Previously, if a host was created by the DCD, then the host property <tt>Creation / Locking > Locked
by</tt> would not be migrated. Instead the site would show <tt>Unknown site (OLD_SITE_ID)</tt> and
the host would no longer be updated by the DCD. With this Werk, the migration is done automatically
during the renaming.
ID: 15610
Title: Fix <tt>Error in LIVESTATUS_TCP_ONLY_FROM</tt> during <tt>omd config</tt>
Component: Site Management
Level: 2
Class: Bug fix
Version: 2.2.0b7
If a user ran the command <tt>omd config</tt> and selected <tt>Distributed Monitoring >
LIVESTATUS_TCP_ONLY_FROM</tt>, then the following error was shown
C+:
Error in LIVESTATUS_TCP_ONLY_FROM
C-:
With this Werk, the error no longer occurs.
ID: 15607
Title: Reduce occurences of Missing data
Component: Setup
Level: 2
Class: Bug fix
Version: 2.3.0b1
The Check_MK service often showed the message
C+:
[piggyback] Missing data WARN
C-:
before a piggyback host was deleted. This lead to many false alarms in dynamic environments such as
Kubernetes. The root cause of this was that the <tt>delete-hosts</tt> automation would delete
piggyback files, which where still in use. With this Werk, the piggyback files are cleaned up by
Check_MK's dedicated housekeeping job (see Werk 5538).
ID: 15466
Title: autodiscovery: Show site changes made by Periodic service discovery
Component: Setup
Level: 2
Class: Bug fix
Version: 2.3.0b1
The werk is incompatible because it removes the 'cmk --discover-marked-hosts' command.
We consider this command an internal one. So it's likely that you don't not need to do anything.
However, if you need access to this command, please let us know.
Previously, if 'Periodic service discovery' was used with 'Automatically update service configuration'
enabled and 'Do not activate changes' activation option, the services would be discovered but
the change wasn't visible in 'Activate pending changes' or in the audit log.
This made it impossible to know whether there are any discovered changes that need to be activated
and what these changes are.
Now, when changes get automatically discovered but not activated, they appear in
'Activate pending changes' and the action is logged to the audit log.
In case of automatic discovery with activation, the action will be logged to the audit log.