Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15969 discussions

Checkmk Werk 13990: Fix systemd_units check plugin crash on certain initial line characters

by Tim Peisker

ID: 13990 Title: Fix systemd_units check plugin crash on certain initial line characters Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 In some cases, the plugin <tt>systemd_units</tt> crashed when parsing raw agent data. In such cases, the Check_MK Discovery service reported "Parsing of section systemd_units failed" and went WARNING. The error message in the corresponding crash report was: C+: IndexError (list index out of range) C-:

2 years, 3 months

Checkmk Werk 14135: KUBE: API timeouts are configured for the /api/v1/resourcequotas endpoint

by Solomon Jacobs

ID: 14135 Title: KUBE: API timeouts are configured for the /api/v1/resourcequotas endpoint Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 When calling the /api/v1/resourcequotas endpoint, the Kubernetes special agent would send a HTTP request, which ignored the TCP timeout options specified in the Kubernetes rule. This could lead to hanging connections. With this werk, this is fixed.

2 years, 3 months

Checkmk Werk 14419: <tt>cisco_cpu_multiitem</tt>, <tt>cisco_fru_module_status</tt>: Fix crash in raw data parsing

by Joerg Herbel

ID: 14419 Title: <tt>cisco_cpu_multiitem</tt>, <tt>cisco_fru_module_status</tt>: Fix crash in raw data parsing Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 For some devices, the check plugins <tt>cisco_cpu_multiitem</tt> and <tt>cisco_fru_module_status</tt> did not discover any services due to a crash in the parsing of the raw data. Instead, the Check_MK Discovery service reported: LI: Parsing of section cisco_cpu_multiitem failed LI: Parsing of section cisco_fru_module_status failed

2 years, 3 months

Checkmk Werk 14356: Windows agent reports Virtual Size correctly

by Sergey Kipnis

ID: 14356 Title: Windows agent reports Virtual Size correctly Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Previously, to report the Virtual size of a process Windows agent used metric 'VirtualSize' from WMI counter 'Win32_Process'. Unfortunately, in Windows this metric means not the Virtual size of process but the size of the process virtual address space, usually 2TB for 32-bit application. As a result monitoring information related to the process Virtial size was useless. Since this release, Windows agent uses 'Commit Charge' Win32 metric to correctly report the Virtual size of a process, thus solving the problem. 'Commit Charge' is the total amount of virtual memory of a process that must be backed by either physical memory or the page file.

2 years, 3 months

Checkmk Werk 14337: Fix painter "Event Console Events/Hosts: Hostname"

by Ronny Bruska

ID: 14337 Title: Fix painter "Event Console Events/Hosts: Hostname" Component: Event Console Level: 1 Class: Bug fix Version: 2.2.0i1 The painter used in e.g. the view "ec_events" points to the view "ec_events_of_host". This view should than show host specific events. In case of SNMP traps, the results were always empty if the host was known to Checkmk because the livestatus query searched for the host name instead of the IP.

2 years, 3 months

Checkmk Werk 13928: validation of custom tag-groups through the REST API

by Christoph Rauch

ID: 13928 Title: validation of custom tag-groups through the REST API Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 To create and edit custom tag groups via the REST API, one had to restart Apache after a new tag was created and before it could be used. This werk fixes this behaviour. A restart is no longer necessary for the tag-groups to be editable right after creation. Note: The documentation of the custom created tags in the ReDoc component are still only updated after an Apache restart. This does not affect the editability of the tags though.

2 years, 3 months

Checkmk Werk 13929: checkbox tag-group handling

by Christoph Rauch

ID: 13929 Title: checkbox tag-group handling Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 In previous versions when a tag-group with only one choice (a checkbox) was set to a folder and subsequently removed on a host in that folder, the "show hosts" REST API call on that folder crashed with a 500 error (with the error: "tag_xxx can not be None"). This werk fixes this behaviour. Apache still needs to be restarted so newly created tag-groups come into effect on the REST API.

2 years, 3 months

Checkmk Werk 13730: check_temperature: Make 'unique_name' and 'value_store' optional, but both are needed for trend computation

by Simon Jess

ID: 13730 Title: check_temperature: Make 'unique_name' and 'value_store' optional, but both are needed for trend computation Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Since Checkmk version 2.1.0 the check_temperature function required {{unique_name}} and {{value_store}}. Both are only needed for trend computation. Now {{unique_name}} and {{value_store}} are optional again. The check engine raises a ValueError if only one of both are set.

2 years, 3 months

Checkmk Werk 13926: validation of error responses of the REST API

by Christoph Rauch

ID: 13926 Title: validation of error responses of the REST API Component: Core & setup Level: 2 Class: Bug fix Version: 2.2.0i1 This werk changes the default error schema to be in line with the until now returned responses. The schema and responses did not fit and it was not found because the responses were not checked automatically. This is now the case. To ensure that dynamic scripts will not break only the schema has been changed. Users of dynamic languages (Python, Bash, etc.) will not have to change anything. If you use a statically generated API client, you may need to re-compile the client after this werk. The changed fields in the schema (not the response) are: - code -> status - message -> detail

2 years, 3 months

Checkmk Werk 13931: wrong labels not raising errors in the REST API

by Christoph Rauch

ID: 13931 Title: wrong labels not raising errors in the REST API Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 Previously when trying to set an invalid "labels" value when creating or updating a host through the REST API, the error did not occur and a 200 OK response would be returned. The value would not be set though. This werk fixes this problem.

2 years, 3 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1