Checkmk werks level1 June 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
272 discussions

[2.4.0] Checkmk Werk 16245 created: Add c6a.* as AWS EC2 resource types

by Checkmk werks level 1

[//]: # (werk v2) # Add c6a.* as AWS EC2 resource types key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-06-11T14:47:20+00:00 level | 1 class | feature component | checks edition | cre

3 months, 1 week

[2.2.0] Checkmk Werk 17050 created: Don't escape customer name

by Checkmk werks level 1

Title: Don't escape customer name Class: fix Compatible: compat Component: wato Date: 1718032736 Edition: cme Level: 1 Version: 2.2.0p28 If you created a customer with e.g. an ampersand in the customer name, the name was escaped on the customers page showing "&amp" instead of "&".

3 months, 1 week

[2.3.0] Checkmk Werk 16509 adapted: Fix notifications postponed forever with Use the status of the service

by Checkmk werks level 1

Werk 16509 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Fix notifications postponed forever with Use the status of the service key | value ---------- | --- date | 2024-02-14T15:45:34+00:00 version | 2.3.0p7 class | fix edition | cee component | notifications level | 1 compatible | yes Configuring a service with "host check command > use the status of the service" would result in notifications for any service to be postponed forever. This has been fixed. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Fix notifications postponed forever with Use the status of the service key | value ---------- | --- date | 2024-02-14T15:45:34+00:00 - version | 2.3.0p6 ? ^ + version | 2.3.0p7 ? ^ class | fix edition | cee component | notifications level | 1 compatible | yes Configuring a service with "host check command > use the status of the service" would result in notifications for any service to be postponed forever. This has been fixed.

3 months, 1 week

[2.3.0] Checkmk Werk 16859 adapted: extreme_vsp_switches_power_supply: Fix crash during discovery

by Checkmk werks level 1

Werk 16859 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # extreme_vsp_switches_power_supply: Fix crash during discovery key | value ---------- | --- date | 2024-06-10T09:32:25+00:00 version | 2.3.0p7 class | fix edition | cre component | checks level | 1 compatible | yes Discovery of `extreme_vsp_switches_power_supply` services crashed in case of VSP input line voltage being `ac110vOr220v` or `dc`. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # extreme_vsp_switches_power_supply: Fix crash during discovery key | value ---------- | --- date | 2024-06-10T09:32:25+00:00 - version | 2.3.0p6 ? ^ + version | 2.3.0p7 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes Discovery of `extreme_vsp_switches_power_supply` services crashed in case of VSP input line voltage being `ac110vOr220v` or `dc`.

3 months, 1 week

[2.3.0] Checkmk Werk 16859 created: extreme_vsp_switches_power_supply: Fix crash during discovery

by Checkmk werks level 1

[//]: # (werk v2) # extreme_vsp_switches_power_supply: Fix crash during discovery key | value ---------- | --- date | 2024-06-10T09:32:25+00:00 version | 2.3.0p6 class | fix edition | cre component | checks level | 1 compatible | yes Discovery of `extreme_vsp_switches_power_supply` services crashed in case of VSP input line voltage being `ac110vOr220v` or `dc`.

3 months, 1 week

[2.3.0] Checkmk Werk 16509 created: Fix notifications postponed forever with Use the status of the service

by Checkmk werks level 1

[//]: # (werk v2) # Fix notifications postponed forever with Use the status of the service key | value ---------- | --- date | 2024-02-14T15:45:34+00:00 version | 2.3.0p6 class | fix edition | cee component | notifications level | 1 compatible | yes Configuring a service with "host check command > use the status of the service" would result in notifications for any service to be postponed forever. This has been fixed.

3 months, 1 week

[2.4.0] Checkmk Werk 16859 created: extreme_vsp_switches_power_supply: Fix crash during discovery

by Checkmk werks level 1

[//]: # (werk v2) # extreme_vsp_switches_power_supply: Fix crash during discovery key | value ---------- | --- date | 2024-06-10T09:32:25+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Discovery of `extreme_vsp_switches_power_supply` services crashed in case of VSP input line voltage being `ac110vOr220v` or `dc`.

3 months, 1 week

[2.4.0] Checkmk Werk 16986 created: Respect lower vertical range limit when rendering graphs

by Checkmk werks level 1

[//]: # (werk v2) # Respect lower vertical range limit when rendering graphs key | value ---------- | --- date | 2024-06-07T12:10:25+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes When rendering a graph with a vertical range that does not comprise all the data, the lower vertical range limit was not respected. Instead, the rendered lines or areas extended into the area below the graph, potentially covering the time axis labels. As of this werk, rendered lines and areas are cut off at the lower vertical range limit.

3 months, 1 week

[2.2.0] Checkmk Werk 17049 created: Add ID to some sections on "Edit role" page

by Checkmk werks level 1

Title: Add ID to some sections on "Edit role" page Class: feature Compatible: compat Component: multisite Date: 1718015289 Edition: cre Level: 1 Version: 2.2.0p28 Built-in views already showed the ID of the view, this was added now for custom views and other sections like dashboards, topics and graph collections.

3 months, 1 week

[2.2.0] Checkmk Werk 16430 adapted: veeam_jobs: Always Monitor Result of Last Backup

by Checkmk werks level 1

Werk 16430 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: veeam_jobs: Always Monitor Result of Last Backup Class: fix Compatible: compat Component: checks Date: 1717598169 Edition: cee Level: 1 Version: 2.2.0p28 Previously, the check plugin <code>veeam_jobs</code> would not always check the result of the last backup job to determine the monitoring state. If the creation time was an empty string, it would show <code>item not found</code>. Moreover, if the last state of the plugin was <code>Starting</code>, <code>Working</code> or <code>Postprocessing</code>, then the check would be OK, even if the last backup failed. The check now shows all the information available unconditionally. Moreover, * a Success result is OK, * a Warning result is WARN, * a Failed result is CRIT, * a None result is OK or UNKNOWN. There is no change in behaviour in this case. ------------------------------------<diff>------------------------------------------- Title: veeam_jobs: Always Monitor Result of Last Backup Class: fix Compatible: compat Component: checks Date: 1717598169 Edition: cee Level: 1 Version: 2.2.0p28 Previously, the check plugin <code>veeam_jobs</code> would not always check the result of the last backup job to determine the monitoring state. If the creation time was - an empty string, it would show <code>item not found</code> in case. It will now show all - the information available and the correct monitoring state. + an empty string, it would show <code>item not found</code>. Moreover, if the last + state of the plugin was <code>Starting</code>, <code>Working</code> or <code>Postprocessing</code>, then the + check would be OK, even if the last backup failed. + The check now shows all the information available unconditionally. Moreover, + * a Success result is OK, + * a Warning result is WARN, + * a Failed result is CRIT, + * a None result is OK or UNKNOWN. There is no change in behaviour in this case. +

3 months, 1 week

← Newer
1
...
15
16
17
18
19
20
21
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2024