Checkmk werks level1 March 2022

checkmk-werks-lvl1@lists.checkmk.com

26 participants
120 discussions

Checkmk Werk 13766: REST API: fix code example for endpoints which use booleans in their query params

by Wontek Hong

ID: 13766 Title: REST API: fix code example for endpoints which use booleans in their query params Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 In the previous version, boolean based query params were excluded from the examples in the REST API documentation. This led to confusion as the params were effectively empty for some endpoints. This werk fixes this and ensures that all query params are shown in the python examples.

2 years, 6 months

Checkmk Werk 13605: win-agent creates allow-legacy-pull on upgrade from 2.0(or earlier) version

by Sergey Kipnis

ID: 13605 Title: win-agent creates allow-legacy-pull on upgrade from 2.0(or earlier) version Component: Checks & agents Level: 2 Class: New feature Version: 2.2.0i1 With this release the unencrypted connection may be allowed only when performing upgrade from version 2.0 or earlier.

2 years, 6 months

Checkmk Werk 13414: Fix copying of views into dashboard

by Benedikt Seidl

ID: 13414 Title: Fix copying of views into dashboard Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 The following error was shown after copying the "allservices" view into a dashboard (create new dashboard; choose "Add" -> "Copy of existing view"; choose "allservices"). <tt>Cannot load dashboards from /omd/sites/site/var/check_mk/web/cmkadmin/user_dashboards.mk: invalid syntax (<unknown>, line 1)</tt> The error was permanent, no dashboards could be viewed or edited. The error could be resolved by removing a single <tt>l</tt> before a <tt>"</tt> from the file mentioned in the error message.

2 years, 6 months

Checkmk Werk 13411: Cisco Prime: Add host options

by Benedikt Seidl

ID: 13411 Title: Cisco Prime: Add host options Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Before this change the ip address was used to connect to the Cisco Prime server. This could lead to problems if a TLS connection was used and the certificate was only valid for the domain and not for the ip address. Now it's possible to choose whether the ip address, the host name or a custom host should be used.

2 years, 6 months

Checkmk Werk 13672: Fix possible KeyError on ruleset page with predifined conditions

by Ronny Bruska

ID: 13672 Title: Fix possible KeyError on ruleset page with predifined conditions Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If a user views a ruleset page with rules containing predefined conditions the user is not permitted for, a KeyError occurs. The ruleset page will now show correctly such rules. If a user with no permission for the used predefined condition edits such rule, the predefined condition field will show a corresponding message that the user has no permission for the choosen predefined condition.

2 years, 6 months

Checkmk Werk 13618: Checkmk free edition ships with same amount of fetcher helpers as enterprise

by Óscar Nájera

ID: 13618 Title: Checkmk free edition ships with same amount of fetcher helpers as enterprise Component: cmc Level: 1 Class: Bug fix Version: 2.2.0i1 Free edition shipped with a reduced count of fetcher helpers, yet when updating to the enterprice version this count remained locked and the enterprice system's performance did not scale on higher load. Thus the free edition ships the same amount of fetchers, which idle under the low load of the free edition, but are able to work upon upgrade.

2 years, 6 months

Checkmk Werk 13817: Add SimpleLevels Valuespec for setup plugins

by Max Linke

ID: 13817 Title: Add SimpleLevels Valuespec for setup plugins Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 To simplify writing setup plugins for levels configuration we added a SimpleLevels valuespec. SimpleLevels allows configuration without predictive levels. If your check plugin supports predictive checks use the Levels valuespec. See the code example for usage: ``` ... from cmk.gui.plugins.wato.utils import SimpleLevels, Levels rulespec_registry.register( CheckParameterRulespecWithItem( check_group_name="your_awesome_check", group=RulespecGroupCheckParametersApplications, match_type="dict", parameter_valuespec=lambda: Dictionary( title=_("Parameters for Check"), elements=[ ("foo_levels_without prediction", SimpleLevels(title=_("Parameters"))), ("bar_levels_with_optional_prediction", Levels(title=_("Parameters"))), ], ), title=lambda: _("An awesome check"), ) ) ```

2 years, 6 months

Checkmk Werk 13578: Do not ignore debian sec updates in apt

by Timotheus Bachinger

ID: 13578 Title: Do not ignore debian sec updates in apt Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 In case a Debian host receives kernel security updates, the apt plugin may miss the data, which results in the service becoming stale. This is fixed now.

2 years, 6 months

Checkmk Werk 13705: Special agents should not produce a check_mk section

by Moritz Kiemer

ID: 13705 Title: Special agents should not produce a check_mk section Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This werk only affects maintainers of custom special agents. Special agents should not produce an <tt>check_mk</tt> section. In the past, writing this section in the output of a special agent offered the possibility to hack a version information into the "Check_MK" service. Since the display of the hosts OS and agent version has been moved out of the "Check_MK" service, this will not only not work anymore, but it will lead to confusing output the new "Check_MK Agent" service. The reasoning behind this change is this: The state (and summary) of the "Check_MK" service should be termined by the successfull or failed <b>operation</b> of the datasources, such as timeouts, refused connections and parsing exceptions. It should not be concerned with the semantics of the received payload. If you want to display the version number of the special agent, you have to implement a dedicated service. However note that the special agent is on the site, not on the monitored host, so its version is not really a property of the monitored host. If you want to use the OS information, you have to write your own plugin. If you care about host labels, consider writing a <tt><<<labels>>></tt> compliant section.

2 years, 6 months

Checkmk Werk 13540: Do not forward data from management board to host specific services if no host data is available

by Simon Jess

ID: 13540 Title: Do not forward data from management board to host specific services if no host data is available Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 In Checkmk 1.6 some plugins where discovered for management boards, but with the regular host plugin name. If a host provides no data then the data from the management board were used. In general this is very confusing and not right at all. With this change these services will go to UNKNOWN. Please rediscover the affected hosts. You may lose the history of these services and your rules may also have to be adapted. Example: An agent-based host has configured a SNMP management board. Then this host has two data sources: the agent data source (host) and the SNMP management board. After the host was discovered two uptime services were found: One service from its own data source and the other one from the management board with the prefix "Management Interface: ". During checking if the host's data source does not provide any data for the uptime service then the data of the management board is used for this service. This results in two uptime services which process the same data.

2 years, 6 months

← Newer
1
...
4
5
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2022