Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15927 discussions

[2.4.0] Checkmk Werk 16527 deleted: ldap_connection: implementation of new ldap connection endpoints

by Checkmk werks level 1

Werk 16527 was deleted. The following Werk is no longer relevant. [//]: # (werk v2) # ldap_connection: implementation of new ldap connection endpoints key | value ---------- | --- date | 2024-03-07T09:59:38+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes This werk implements endpoints that provide a way to manage LDAP connections via the REST-API in the same way the user interface does. This includes creating, updating, deleting and listing LDAP connections.

6 months, 2 weeks

[2.3.0] Checkmk Werk 16114 adapted: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one

by Checkmk werks level 1

Werk 16114 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one Class: fix Compatible: compat Component: rest-api Date: 1696846527 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API. For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API. This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters. ------------------------------------<diff>------------------------------------------- Title: folder_config: Extend GET and DELETE endpoints folder name pattern to match the CREATE enpoint one Class: fix Compatible: compat Component: rest-api Date: 1696846527 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 - Previously, the folder name pattern for GET and DELETE endpoints were stricter than the CREATE, provoking that a new folder could not be retrieved nor deleted. This fix widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one. + Prior to this Werk, the folder name pattern for GET and DELETE endpoints did not allow the use of unicode characters while they were supported by the CREATE endpoint, with the result that folders created with such characters could not be accessed or deleted from the REST API. + + For example, the user was able to create a folder named û亿Ï8Ĺ, which then could not be read or deleted from the API. + + This Werk widens the folder name pattern on GET and DELETE endpoints to align with the CREATE one and now all of them support unicode characters.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16527 created: ldap_connection: implementation of new ldap connection endpoints

by Checkmk werks level 1

[//]: # (werk v2) # ldap_connection: implementation of new ldap connection endpoints key | value ---------- | --- date | 2024-03-07T09:59:38+00:00 version | 2.4.0b1 class | feature edition | cre component | rest-api level | 1 compatible | yes This werk implements endpoints that provide a way to manage LDAP connections via the REST-API in the same way the user interface does. This includes creating, updating, deleting and listing LDAP connections.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16496 created: agent_azure: fix parsing loadbalancer data

by Checkmk werks level 1

[//]: # (werk v2) # agent_azure: fix parsing loadbalancer data key | value ---------- | --- date | 2024-03-06T15:46:21+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The agent would crash if information (backend pools or outbound rules) was missing for a load balancer. This werk ensures that the system handles scenarios where this data may not be present.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16383 created: Handle empty operational status during interface inventory

by Checkmk werks level 1

[//]: # (werk v2) # Handle empty operational status during interface inventory key | value ---------- | --- date | 2024-03-14T13:48:35+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes `inv_if.py` crashed on empty oper_status. This is fixed now as at least on some Cisco ASA/FirePower devices this value is empty.

6 months, 2 weeks

[2.2.0] Checkmk Werk 16609 created: Publish permission handling for various components

by Checkmk werks level 1

Title: Publish permission handling for various components Class: fix Compatible: incomp Component: multisite Date: 1710410065 Edition: cre Level: 1 Version: 2.2.0p24 Werk 13498 introduced the possibility to set limit publish permissions to certain contact groups, sites etc. Still, the permission "Publish views" (e.g. for publishing views) was needed to see the published views. With Werk 16320 this has been fixed for dashboards, views and reports. This werk fixes the behavior for the remaining components (Bookmarks, Graphs, SLAs and Reports). Note: Please check the respective publish configuration.

6 months, 2 weeks

[2.2.0] Checkmk Werk 16625 created: service_discovery/bulk_discovery: reformulate documentation for mode option

by Checkmk werks level 1

Title: service_discovery/bulk_discovery: reformulate documentation for mode option Class: fix Compatible: compat Component: rest-api Date: 1710239567 Edition: cre Level: 1 Version: 2.2.0p24 Previously, the single service discovery and the bulk discovery shared the same documentation for the mode field. This covers the use cases for the bulk discovery to a certain degree. This werk fixes this. In addition, this werk also resolves previously non working modes 'fix_all' and 'tabula_rasa'.

6 months, 2 weeks

[2.2.0] Checkmk Werk 16550 created: Linux remote alert handlers not running under non-root user

by Checkmk werks level 1

Title: Linux remote alert handlers not running under non-root user Class: fix Compatible: compat Component: agents Date: 1710234878 Edition: cee Level: 1 Version: 2.2.0p24 In the ruleset <em>Remote alert handlers (Linux)</em>, you have to specify a user under that the remote alert handler will be executed on agent side. This user is set to <em>root</em> by default, but it's possible to choose an arbitrary user. But, when choosing a non-root user, the alert handlers previously failed to execute, because the handler files got deployed with root-ownership and were not readable by others. To fix the problem, the ownership of the files now get changed to the specified user. Security note: In general, it's important that all internal files of the Checkmk agent have root ownership, as they might be read/executed by the Checkmk agent under root. However, this is not the case for remote alert handlers, as they always get executed under the specified user. As an additional security measure, the dispatcher on agent side checks the ownership of installed remote alert handlers, and refuses to execute non-root owned handlers when called via SSH with root rights.

6 months, 2 weeks

[2.2.0] Checkmk Werk 16599 created: jolokia metrics: restores 'default product' behavior

by Checkmk werks level 1

Title: jolokia metrics: restores 'default product' behavior Class: fix Compatible: compat Component: checks Date: 1710165014 Edition: cre Level: 1 Version: 2.2.0p24 The check plugin no longer showed any metrics if a product was not specified in the ruleset configuration. This werk restores the original behaviour, using as a default product the one reported in the info section of the agent output.

6 months, 2 weeks

[2.4.0] Checkmk Werk 16175 created: apc_netbotz_sensors, apc_netbotz_other_sensors: Add monitoring for Netbotz 50 devices

by Checkmk werks level 1

[//]: # (werk v2) # apc_netbotz_sensors, apc_netbotz_other_sensors: Add monitoring for Netbotz 50 devices key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-03-08T10:39:25+00:00 level | 1 class | feature component | checks edition | cre apc_netbotz_sensors and apc_netbotz_other_sensors checks provided monitoring for APC Netbotz v2 devices. Now, the checks can additionally monitor APC Netbotz 50 devices.

6 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1