Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16154 discussions

[2.4.0] Checkmk Werk 16744 created: Fix internal error while combining inventory tables within views

by Checkmk werks level 1

[//]: # (werk v2) # Fix internal error while combining inventory tables within views key | value ---------- | --- date | 2024-06-13T16:35:39+00:00 version | 2.4.0b1 class | fix edition | cre component | multisite level | 1 compatible | yes

5 months

[2.4.0] Checkmk Werk 16512 created: Restart scheduler after setting "use the status of a service"

by Checkmk werks level 1

[//]: # (werk v2) # Restart scheduler after setting "use the status of a service" key | value ---------- | --- date | 2024-06-13T14:21:01+00:00 version | 2.4.0b1 class | fix edition | cee component | core level | 1 compatible | yes This fixes the case where the default check scheduler would not restart after the user temporarily set "use the status of service" as the "host check command". The corresponding log entry was "refuse to schedule invalid jobhost ... at 1970-0101 ...".

5 months

[2.4.0] Checkmk Werk 17052 created: mkeventd: Forward to remote Event Console or Syslog server if configured

by Checkmk werks level 1

[//]: # (werk v2) # mkeventd: Forward to remote Event Console or Syslog server if configured key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-06-13T13:10:59+00:00 level | 1 class | fix component | notifications edition | cre The notification method "Forward notification to Event Console" offers the option to forward messages to a remote Event Console or Syslog server. In earlier versions the messages were only forwarded if the local Event Console (mkeventd) was not running. This has been fixed.

5 months

[2.4.0] Checkmk Werk 17051 created: Test notifications: Match labels for hosts on remote sites

by Checkmk werks level 1

[//]: # (werk v2) # Test notifications: Match labels for hosts on remote sites key | value ---------- | --- date | 2024-06-11T17:19:29+00:00 version | 2.4.0b1 class | fix edition | cre component | notifications level | 1 compatible | yes Labels of hosts from remote sites were not added to the notification context. This results in no match on testing a label condition, even the host had the label configured. Hosts on the central site were not affected.

5 months

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

by Checkmk werks level 1

[//]: # (werk v2) # Don't escape customer name key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-06-10T15:18:56+00:00 level | 1 class | fix component | wato edition | cme 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 "&".

5 months

[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, <ul> <li> a Success result is OK,</li> <li> a Warning result is WARN,</li> <li> a Failed result is CRIT,</li> <li> a None result is OK or UNKNOWN. There is no change in behaviour in this case.</li> </ul> ------------------------------------<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>. 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. + <ul> + <li> a Success result is OK,</li> + <li> a Warning result is WARN,</li> + <li> a Failed result is CRIT,</li> + <li> a None result is OK or UNKNOWN. There is no change in behaviour in this case.</li> + </ul> +

5 months

[2.3.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. [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.3.0p6 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` 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 `item not found`. Moreover, if the last state of the plugin was `Starting`, `Working` or `Postprocessing`, 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>------------------------------------------- [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.3.0p6 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` 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 `item not found`. Moreover, if the last state of the plugin was `Starting`, `Working` or `Postprocessing`, 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.

5 months

[2.4.0] Checkmk Werk 16827 created: Fix checkmk errors appearing at the bottom of the page

by Checkmk werks level 1

[//]: # (werk v2) # Fix checkmk errors appearing at the bottom of the page key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-05-28T16:05:26+00:00 level | 1 class | fix component | wato edition | cre A certain class of errors, including time out errors appeared at the bottom of a page, making the error difficult to notice, especially when viewing large tables. With this werk, these error messages will appear on top of the page like all other errors.

5 months

[2.4.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. [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.4.0b1 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` 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 `item not found`. Moreover, if the last state of the plugin was `Starting`, `Working` or `Postprocessing`, 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>------------------------------------------- [//]: # (werk v2) # veeam_jobs: Always Monitor Result of Last Backup key | value ---------- | --- date | 2024-06-05T14:36:09+00:00 version | 2.4.0b1 class | fix edition | cee component | checks level | 1 compatible | yes Previously, the check plugin `veeam_jobs` 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 `item not found`. Moreover, if the last state of the plugin was `Starting`, `Working` or `Postprocessing`, 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.

5 months

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

by Checkmk werks level 1

Title: Add c6a.* as AWS EC2 resource types Class: feature Compatible: compat Component: checks Date: 1718117240 Edition: cre Level: 1 Version: 2.2.0p28

5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1