Checkmk werks level1 December 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
128 discussions

[2.1.0] Checkmk Werk 16276 created: "Cisco Devices: Temperature Sensors" used wrong lower device levels

by Checkmk werks level 1

Title: "Cisco Devices: Temperature Sensors" used wrong lower device levels Class: fix Compatible: compat Component: checks Date: 1702899571 Edition: cre Level: 1 Version: 2.1.0p38 The services picked the device levels meant for a "less than" comarison, when in fact comparing "less or equal" (as Checkmk usually does). They now pick the levels meant for "less or equal" comparison.

9 months

[2.2.0] Checkmk Werk 16276 created: "Cisco Devices: Temperature Sensors" used wrong lower device levels

by Checkmk werks level 1

Title: "Cisco Devices: Temperature Sensors" used wrong lower device levels Class: fix Compatible: compat Component: checks Date: 1702899571 Edition: cre Level: 1 Version: 2.2.0p18 The services picked the device levels meant for a "less than" comarison, when in fact comparing "less or equal" (as Checkmk usually does). They now pick the levels meant for "less or equal" comparison.

9 months

[2.3.0] Checkmk Werk 16276 created: "Cisco Devices: Temperature Sensors" used wrong lower device levels

by Checkmk werks level 1

[//]: # (werk v2) # "Cisco Devices: Temperature Sensors" used wrong lower device levels key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-12-18T11:39:31+00:00 level | 1 class | fix component | checks edition | cre The services picked the device levels meant for a "less than" comarison, when in fact comparing "less or equal" (as Checkmk usually does). They now pick the levels meant for "less or equal" comparison.

9 months

[2.3.0] Checkmk Werk 15317 created: primekey_fan: rename service description to 'Primekey Fan'

by Checkmk werks level 1

[//]: # (werk v2) # primekey_fan: rename service description to 'Primekey Fan' key | value ---------- | --- date | 2023-12-20T09:43:06+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | no You are affected by this change if you monitor a Primekey appliance and use searches or rules that rely on the service description. In order to unify the primeky checks `primekey_fan` services description was renamed from 'Fan Primekey' to 'Primekey Fan'.

9 months

[2.1.0] Checkmk Werk 16289 created: jolokia_jvm_memory: translate old heap and nonheap metrics

by Checkmk werks level 1

Title: jolokia_jvm_memory: translate old heap and nonheap metrics Class: fix Compatible: compat Component: checks Date: 1699881953 Edition: cre Knowledge: doc Level: 1 Version: 2.1.0p38

9 months

[2.2.0] Checkmk Werk 16289 created: jolokia_jvm_memory: translate old heap and nonheap metrics

by Checkmk werks level 1

Title: jolokia_jvm_memory: translate old heap and nonheap metrics Class: fix Compatible: compat Component: checks Date: 1699881953 Edition: cre Level: 1 Version: 2.2.0p18

9 months

[2.2.0] Checkmk Werk 16036 created: host_config: 500 status code with no explicit IPMI credentials configured

by Checkmk werks level 1

Title: host_config: 500 status code with no explicit IPMI credentials configured Class: fix Compatible: compat Component: rest-api Date: 1702993286 Edition: cre Level: 1 Version: 2.2.0p18 When calling the <code>host_config/collections/all</code> endpoint with IPMI credentials activated and set to <code>No explicit credentials</code> the endpoint returns a status 500 (Internal Server Error). Now the information is correctly returned.

9 months

[2.3.0] Checkmk Werk 16289 created: jolokia_jvm_memory: translate old heap and nonheap metrics

by Checkmk werks level 1

[//]: # (werk v2) # jolokia_jvm_memory: translate old heap and nonheap metrics key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-11-13T13:25:53+00:00 level | 1 class | fix component | checks edition | cre

9 months

[2.3.0] Checkmk Werk 16036 created: host_config: 500 status code with no explicit IPMI credentials configured

by Checkmk werks level 1

[//]: # (werk v2) # host_config: 500 status code with no explicit IPMI credentials configured key | value ---------- | --- date | 2023-12-19T13:41:26+00:00 version | 2.3.0b1 class | fix edition | cre component | rest-api level | 1 compatible | yes When calling the `host_config/collections/all` endpoint with IPMI credentials activated and set to `No explicit credentials` the endpoint returns a status 500 (Internal Server Error). Now the information is correctly returned.

9 months

[2.2.0] Checkmk Werk 15316 created: solaris: uptime: Cannot render negative timespan

by Checkmk werks level 1

Title: solaris: uptime: Cannot render negative timespan Class: fix Compatible: compat Component: checks Date: 1702991355 Edition: cre Level: 1 Version: 2.2.0p18 Solaris server may keep a bad time when moved to different hardware. This is corrected some minutes after booting via NTP server. If the checkmk client is used before the time has been corrected, it was possible that a negative time span was reported for the time since the last start. This caused a crash in the check. The new behaviour is, that the check will report an UNKNOWN status alongside the message: "Your Solaris system reported to be booted in the future."

9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2023