Checkmk werks level1 January 2023

checkmk-werks-lvl1@lists.checkmk.com

25 participants
89 discussions

Checkmk Werk 15121: Fix possible AssertionError on rule search

by Ronny Bruska

ID: 15121 Title: Fix possible AssertionError on rule search Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If you e.g. searched for tags in the rule search, an error like "AssertionError" could occur.

1 year, 6 months

Checkmk Werk 14792: Enable pip install of packages as site user

by Timotheus Bachinger

ID: 14792 Title: Enable pip install of packages as site user Component: Site Management Level: 1 Class: Bug fix Version: 2.2.0i1 In case you want to install python packages with pip as a site user, which needs to be compiled from source, this should now be possible. One use case for this would be the installation of ibm_db which is needed for the active check "check_sql": C+: python3 -m pip -vvv install --user ibm_db C-:

1 year, 6 months

Checkmk Werk 15202: Allow mk_oracle plugin in /tmp directory

by Rebekka Seltmann

ID: 15202 Title: Allow mk_oracle plugin in /tmp directory Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This change is relevant if you are monitoring oracle databases and want to use the mk_oracle plugin from within the /tmp directoy. Previously, this conflicted with the temporary directory of the same name created by the plugin. This has now been fixed.

1 year, 6 months

Checkmk Werk 14575: OpenShift: Introduce Monitoring

by Solomon Jacobs

ID: 14575 Title: OpenShift: Introduce Monitoring Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 Checkmk now supports monitoring OpenShift clusters. The OpenShift monitoring builds on top of Checkmk's existing Kubernetes monitoring. However, the metrics are collected via methods tailored to OpenShift due to the incompatibility of the <tt>Checkmk collectors</tt> with OpenShift. This new monitoring leverages the Kubernetes API and the off-the-shelf Prometheus monitoring stack of OpenShift. Thus, no additional workload needs to be deployed in your OpenShift cluster. In particular, the OpenShift monitoring does not require the <tt>Checkmk Cluster collector</tt>. This feature can be enabled by configuring the rule <tt>Kubernetes</tt>. Enabling the collectors has the following benefits. <ul> <li>Allow monitoring CPU and Memory usage via the <tt>kube_memory</tt> and <tt>kube_cpu</tt> checks.</li> <li>Enable machine level monitoring on each node.</li> <li>Populate the Kubernetes dashboard with data.</li> </ul> The following check plugins are part of machine-level monitoring of a node. <ul> <li>uptime</li> <li>cpu_loads</li> <li>kernel_util</li> <li>mem_used</li> <li>mem_used (inventory plugin)</li> <li>diskstat</li> <li>df</li> </ul> While Prometheus acts as a data source for the OpenShift monitoring, this does not imply that this monitoring is compatible to any Prometheus stack. For compatibility Checkmk requires the identical set-up of Prometheus as in OpenShift. This includes scraping the same collectors, renaming metrics in the same manner, having the same recording rules and so forth. Thus, we highly recommend using the <tt>Checkmk collectors</tt> for any non-OpenShift Kubernetes environment.

1 year, 6 months

Checkmk Werk 15086: HW/SW Inventory views: Join inventory tables

by Simon Jess

ID: 15086 Title: HW/SW Inventory views: Join inventory tables Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 Inventory based views, ie. the data source is an inventory table, now offer the possibility to join other inventory tables. This can be configured in the related view editor dialog. First you have to choose one or more so-called macros. These macros are based on the columns of this data source and are used to identify a row besides other identifiers like host name. Then these macros can be used for {{Joined inventory columns}} below {{Columns}} in order to connect these tables. Note that these macros only make sense for tables to be connected which also provide these columns. Example: <ul> <li>Choose {{Oracle instances}} as the data source</li> <li>Choose {{SID}} with {{$SID$}} below macros</li> <li>Now you can connect {{Oracle dataguard statistics > Name}} where {{SID}} equals {{$SID$}} below {{match criteria}}</li> </ul> Note: Columns of the data source itself are available below {{Column}} - not {{Joined inventory columns}}.

1 year, 6 months

Checkmk Werk 14393: Warn about User IDs that become incompatible in 2.2.0

by Hannes Rantzsch

ID: 14393 Title: Warn about User IDs that become incompatible in 2.2.0 Component: Setup Level: 1 Class: New feature Version: 2.2.0i1 Beginning with Checkmk version 2.2.0, the use of certain special characters in user IDs will no longer be allowed. As a result, some user IDs that were previously valid in Checkmk version 2.1.0 will become invalid in version 2.2.0. This will affect both local users and users from external connections such as LDAP. With this Werk you will be warned about users that will become incompatible in the future. When you run the `omd update` command, it display a warning message including the list of affected users. Moreover, the Setup > Users page in WATO it will also display a warning message if incompatible user IDs are found. To be compatible with Checkmk version 2.2.0 please ensure that all user IDs adhere to the following restrictions: The first character of a user ID must be a digit, an ASCII letter, an underscore (<tt>_</tt>), or a dollar sign (<tt>$</tt>). The rest of the user ID may additionally contain dash (<tt>-</tt>), at (<tt>@</tt>), and dot (<tt>.</tt>). (In addition to ASCII letters, some umlauts continue to be permitted). If you require certain characters that would no longer be allowed and changing user IDs is not feasible in your system, please contact Checkmk support for assistance.

1 year, 6 months

Checkmk Werk 15174: Process (<tt>ps</tt>) monitoring: Handle processes with empty command lines

by Joerg Herbel

ID: 15174 Title: Process (<tt>ps</tt>) monitoring: Handle processes with empty command lines Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The service discovery for processes crashed if the agent output contained processes which have an emtpy command line and exact process name matching was selected in the process discovery ruleset. Processes with empty command lines can occur eg. on Linux systems (<tt>ps</tt> command) due mandatory access control or in containerized environments.

1 year, 6 months

Checkmk Werk 15111: Bring back some ALLNET IP-Sensoric services

by Moritz Kiemer

ID: 15111 Title: Bring back some ALLNET IP-Sensoric services Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Due to changes and a small bug in the ALLNET IP-Sensoric API the temperature and pressure services have not been discovered.

1 year, 6 months

Checkmk Werk 15060: EventConsole: Allow withdrawal of acknowledge command

by Gav

ID: 15060 Title: EventConsole: Allow withdrawal of acknowledge command Component: REST API Level: 1 Class: New feature Version: 2.2.0i1 Event console events can currently be acknowledged via the REST API, however, to align with the GUI functionality, this change will allow the user to also withdraw the acknowledgemnt via the REST API. As a result of this change, the user can also ack all open events or withdraw all acked events.

1 year, 6 months

Checkmk Werk 15086: HW/SW Inventory views: Join inventory tables

by Simon Jess

1 year, 6 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 January 2023