Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15938 discussions

[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, 1 week

[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, 1 week

[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, 1 week

[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, 1 week

[2.2.0] Checkmk Werk 15315 created: solaris: uptime: AssertionError

by Checkmk werks level 1

Title: solaris: uptime: AssertionError Class: fix Compatible: compat Component: checks Date: 1702989839 Edition: cre Level: 1 Version: 2.2.0p18 Shortly after rebooting, solaris uptime command returned a timestamp that could not be parsed by the checkmk agent.

9 months, 1 week

[2.2.0] Checkmk Werk 16209 created: downtimes: Fix performance issues when creating downtimes

by Checkmk werks level 1

Title: downtimes: Fix performance issues when creating downtimes Class: fix Compatible: compat Component: rest-api Date: 1703062568 Edition: cre Level: 1 Version: 2.2.0p18 This Werk fixes a performance issue that occurred when creating downtimes for services in a distributed monitoring environment.

9 months, 1 week

[2.2.0] Checkmk Werk 16208 created: time_period: Fix error when updating a time period without changing its alias

by Checkmk werks level 1

Title: time_period: Fix error when updating a time period without changing its alias Class: fix Compatible: compat Component: rest-api Date: 1702559447 Edition: cre Level: 1 Version: 2.2.0p18 Prior to this Werk, when updating a time period keeping the same alias, it would raise an error due to the alias already being in use. This fix changes that and performs the requested update.

9 months, 1 week

[2.2.0] Checkmk Werk 16284 created: host_tag_group: add help field to the response schema

by Checkmk werks level 1

Title: host_tag_group: add help field to the response schema Class: fix Compatible: compat Component: rest-api Date: 1702382101 Edition: cre Level: 1 Version: 2.2.0p18

9 months, 1 week

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

by Checkmk werks level 1

[//]: # (werk v2) # solaris: uptime: Cannot render negative timespan key | value ---------- | --- date | 2023-12-19T13:09:15+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | yes 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, 1 week

[2.3.0] Checkmk Werk 15315 created: solaris: uptime: AssertionError

by Checkmk werks level 1

[//]: # (werk v2) # solaris: uptime: AssertionError key | value ---------- | --- date | 2023-12-19T12:43:59+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Shortly after rebooting, solaris uptime command returned a timestamp that could not be parsed by the checkmk agent.

9 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1