Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15873 discussions

[2.3.0] Checkmk Werk 17091 created: missing error message for wrong backup key password

by Checkmk werks level 1

[//]: # (werk v2) # missing error message for wrong backup key password key | value ---------- | --- date | 2024-07-02T12:50:08+00:00 version | 2.3.0p10 class | fix edition | cre component | wato level | 1 compatible | yes When a wrong password was entered for downloading a backup encryption key or a signature key for signing agents, an empty error message box was displayed. Now, the error message is displayed correctly.

2 months, 1 week

[2.3.0] Checkmk Werk 17114 created: esx_vsphere_objects: Allow configuration of "Stand by" state

by Checkmk werks level 1

[//]: # (werk v2) # esx_vsphere_objects: Allow configuration of "Stand by" state key | value ---------- | --- date | 2024-07-10T08:08:33+00:00 version | 2.3.0p10 class | fix edition | cre component | checks level | 1 compatible | yes

2 months, 1 week

[2.3.0] Checkmk Werk 17117 created: multipath: Allow for dots in the UUID

by Checkmk werks level 1

[//]: # (werk v2) # multipath: Allow for dots in the UUID key | value ---------- | --- date | 2024-07-10T15:17:28+00:00 version | 2.3.0p10 class | fix edition | cre component | checks level | 1 compatible | yes Previously devices with dots in their UUID have not been discovered.

2 months, 1 week

[2.4.0] Checkmk Werk 17064 adapted: ServiceNow: Support for update of incidents and cases

by Checkmk werks level 1

Werk 17064 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # ServiceNow: Support for update of incidents and cases key | value ---------- | --- date | 2024-07-08T10:49:12+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes The notification plugin for ServiceNow is now able to update incidents and cases, so if e.g. a state change from OK to WARN created a ticket, a later state change from WARN to CRIT will update the incident or case. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # Servicenow: Support for update of incidents and cases ? ^ + # ServiceNow: Support for update of incidents and cases ? ^ key | value ---------- | --- date | 2024-07-08T10:49:12+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes - The notification plugin for Servicenow is now able to update incidents and ? ------- + The notification plugin for ServiceNow is now able to update incidents and ? +++++++ cases, so if e.g. a state change from OK to WARN created a ticket, a later state change from WARN to CRIT will update the incident or case.

2 months, 1 week

[2.4.0] Checkmk Werk 17065 adapted: ServiceNow: Add option to use custom fields

by Checkmk werks level 1

Werk 17065 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # ServiceNow: Add option to use custom fields key | value ---------- | --- date | 2024-07-08T13:34:21+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes You can now use the "Custom fields" option in the parameters of the ServiceNow notification plugin to add custom fields of your incident or case template. This is useful if you have configured mandatory custom fields within ServiceNow that have to be filled on creation, update oder close of an incident or case. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # Servicenow: Add option to use custom fields ? ^ + # ServiceNow: Add option to use custom fields ? ^ key | value ---------- | --- date | 2024-07-08T13:34:21+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes - You can now use the "Custom fields" option in the parameters of the Servicenow ? ^ + You can now use the "Custom fields" option in the parameters of the ServiceNow ? ^ notification plugin to add custom fields of your incident or case template. - This is useful if you have configured mandatory custom fields within Servicenow ? ^ + This is useful if you have configured mandatory custom fields within ServiceNow ? ^ that have to be filled on creation, update oder close of an incident or case.

2 months, 1 week

[2.4.0] Checkmk Werk 17066 adapted: ServiceNow: New option for authentication with OAuth token

by Checkmk werks level 1

Werk 17066 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # ServiceNow: New option for authentication with OAuth token key | value ---------- | --- date | 2024-07-09T06:27:58+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes You can now use OAuth token to authenticate against your ServiceNow instance. The token can be entered in the new authentication section within the notification method configuration if you choose "OAuth token authentication". For configuration of OAuth within ServiceNow, please refer to the ServiceNow documentation. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) - # Servicenow: New option for authentication with OAuth token ? ^ + # ServiceNow: New option for authentication with OAuth token ? ^ key | value ---------- | --- date | 2024-07-09T06:27:58+00:00 version | 2.4.0b1 class | feature edition | cee component | notifications level | 1 compatible | yes - You can now use OAuth token to authenticate against your Servicenow instance. ? ^ + You can now use OAuth token to authenticate against your ServiceNow instance. ? ^ The token can be entered in the new authentication section within the notification method configuration if you choose "OAuth token authentication". - For configuration of OAuth within Servicenow, please refer to the Servicenow ? ^ ^ + For configuration of OAuth within ServiceNow, please refer to the ServiceNow ? ^ ^ documentation.

2 months, 1 week

[2.4.0] Checkmk Werk 17117 created: multipath: Allow for dots in the UUID

by Checkmk werks level 1

[//]: # (werk v2) # multipath: Allow for dots in the UUID key | value ---------- | --- date | 2024-07-10T15:17:28+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Previously devices with dots in their UUID have not been discovered.

2 months, 1 week

[2.4.0] Checkmk Werk 17114 created: esx_vsphere_objects: Allow configuration of "Stand by" state

by Checkmk werks level 1

[//]: # (werk v2) # esx_vsphere_objects: Allow configuration of "Stand by" state key | value ---------- | --- date | 2024-07-10T08:08:33+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes

2 months, 1 week

[2.3.0] Checkmk Werk 17072 created: Fix "Parsing of section rmon_stats failed" for Cisco SNMP devices

by Checkmk werks level 1

[//]: # (werk v2) # Fix "Parsing of section rmon_stats failed" for Cisco SNMP devices key | value ---------- | --- date | 2024-07-10T07:45:41+00:00 version | 2.3.0p10 class | fix edition | cre component | checks level | 1 compatible | no For certain Cisco devices, the _Check\_MK Discovery_ service and the service discovery page displayed the error message mentioned above. To solve this issue, users have to execute the _Remove all and find new_ action in the actions menu of the service discovery page for affected hosts.

2 months, 1 week

[2.4.0] Checkmk Werk 16563 created: Ensure background jobs finish properly on stopping sites

by Checkmk werks level 1

[//]: # (werk v2) # Ensure background jobs finish properly on stopping sites key | value ---------- | --- date | 2024-07-09T14:38:01+00:00 version | 2.4.0b1 class | fix edition | cre component | core level | 2 compatible | yes Previously running background jobs were not properly cleaned up by `omd stop`. Those processes were terminated at the end of `omd stop` command which would clean up the processes in most cases, but lead to failed jobs and leave crash reports behind. Secondly a few background jobs depend on Redis. In case Redis is stopped while the jobs are still running, the jobs would fail and also leave a crash report behind. This change aims to solve both issues, by extending what happens during `omd stop`. The procedure roughly works like this: 1. First the apache process and site cron are stopped to prevent the start of new background jobs. This is done by the already existing logic. 2. The new init script `background-jobs` gives the jobs some time to finish. Ideally all jobs are stopped after 20 seconds. 3. The stop command does not have to forcefully kill the jobs anymore in this case. 4. As a last resort `omd stop` will terminate the still running jobs as before.

2 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1