Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Checkmk Werk 15892: ntop_alerts: rename alert tabs in ntop alerts dashboard

by Checkmk werks level 2

ID: 15892 Title: ntop_alerts: rename alert tabs in ntop alerts dashboard Component: cmc Level: 3 Class: Bug fix Version: 2.3.0b1 Previously, the alert tabs were named Engaged, Host, Flow. This didn't align correctly with ntopng's own dashboard. They have now been renamed to Engaged Host, Past Host and Past Flow.

1 year, 2 months

Checkmk Werk 15893: ntop_alerts: introduce pagination to ntop alerts dashboard backend

by Checkmk werks level 2

ID: 15893 Title: ntop_alerts: introduce pagination to ntop alerts dashboard backend Component: cmc Level: 3 Class: Bug fix Version: 2.3.0b1 Previously the alerts dashboard would fetch 5 hours of alert data by default or the time range selected by the user via the time series graphs. This caused performance issues since the number of alerts could vary greatly, often resulting in timeouts. This werk addresses this problem by introducing pagination on the backend. We now only fetch 20 alerts in any given api call. The user can then request more using the next button.

1 year, 2 months

Checkmk Werk 15830: Prevent Windows agent service crash in some cases

by Checkmk werks level 2

ID: 15830 Title: Prevent Windows agent service crash in some cases Component: Checks & agents Level: 2 Class: Bug fix Version: 2.2.0p5 In some cases Windows may report non-valid path for a running process. This situation led to a crash of the Windows agent service. With this release, Windows agent is ignoring non-valid path, thus eliminating the problem.

1 year, 2 months

Checkmk Werk 15754: Enable AES-192 and AES-256 privacy protocols for SNMP

by Checkmk werks level 2

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.

1 year, 3 months

Checkmk Werk 15493: Adjustments to local extensions may be required

by External contributor

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. 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. For 2.2 we tried to keep compatibility for the most extensions but could not make sure to cover them all. Therefore, we would like to give you a few examples, how to adjust local extensions if you see incompatibilities with Checkmk 2.2. Please note: Each example stands for one possible import problem, so the module names are interchangeable. Loading "metrics/my_custom_file" failed: No module named 'cmk.gui.plugins.metrics.check_mk' 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-: Loading "views/my_custom_file" failed: name 'inventory_displayhints' is not defined 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-: Loading "wato/my_custom_file" failed: cannot import name 'RulespecGroupIntegrateOtherServices' from 'cmk.gui.plugins.wato.active_checks' 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-: Loading "wato/my_custom_file" failed: name 'socket' is not defined 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. Also see related werks: <a href='https://checkmk.com/werk/13094'>Werk #13094: Various ValueSpec-related API cleanups</a>

1 year, 4 months

Move of mailinglists to lists.checkmk.com

by Alex Wilms

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

1 year, 4 months

Checkmk Werk 15611: Migrate <tt>Locked by</tt> during site renamings

by External contributor

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.

1 year, 4 months

Checkmk Werk 15610: Fix <tt>Error in LIVESTATUS_TCP_ONLY_FROM</tt> during <tt>omd config</tt>

by External contributor

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.

1 year, 4 months

Checkmk Werk 15607: Reduce occurences of Missing data

by Solomon Jacobs

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).

1 year, 4 months

Checkmk Werk 15466: autodiscovery: Show site changes made by Periodic service discovery

by Sofia Colakovic

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.

1 year, 4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2