Checkmk werks level1 September 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
112 discussions

[2.1.0] Checkmk Werk 16059 created: Fix possible failed notifications running in docker environment

by Checkmk werks level 1

Title: Fix possible failed notifications running in docker environment Class: fix Compatible: compat Component: notifications Date: 1695386294 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p34 Werk #15941 already fixed failed notifications on appliances if one recipient had no Email address configured. We have now seen the same behaviour when running Checkmk in a docker container because Nullmailer can not handle such recipients.

7 months, 3 weeks

[2.1.0] Checkmk Werk 16002 created: veeam_cdp_jobs: Fix parsing of last sync which may contain floats like '123,456'

by Checkmk werks level 1

Title: veeam_cdp_jobs: Fix parsing of last sync which may contain floats like '123,456' Class: fix Compatible: compat Component: checks Date: 1695814041 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p34

7 months, 3 weeks

[2.1.0] Checkmk Werk 15999 created: cisco_cpu_multiitem, cisco_fru_module_status: Fix parsing PhysicalClasses

by Checkmk werks level 1

Title: cisco_cpu_multiitem, cisco_fru_module_status: Fix parsing PhysicalClasses Class: fix Compatible: compat Component: checks Date: 1695802874 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p34

7 months, 3 weeks

[2.1.0] Checkmk Werk 15835 created: Fetcher handles timeout correctly

by Checkmk werks level 1

Title: Fetcher handles timeout correctly Class: fix Compatible: compat Component: checks Date: 1695807506 Edition: cre Knowledge: doc Level: 2 State: unknown Version: 2.1.0p34 Previously, a fetcher could miss a timeout, thus creating a problem for monitoring because the number of available fetchers is limited. With this release the problem has been eliminated.

7 months, 3 weeks

[2.2.0] Checkmk Werk 16137 created: user_config: allow update of custom user attributes

by Checkmk werks level 1

Title: user_config: allow update of custom user attributes Class: fix Compatible: incomp Component: rest-api Date: 1695731850 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p11 This werk addresses an issue reported, where you could create a user with custom attributes, but you could not update the user's custom attributes. E.g. Calling this endpoint with the following payload would work, providing the custom attribute 'attr_1' exists. POST check_mk/api/v1/domain-types/user_config/collections/all C+: { "username": "user_1", "fullname": "user_1", "auth_option": { "auth_type": "password", "password": "password_with_at_least_12_characters" }, "disable_login": false, "contact_options": { "email": "user(a)example.com" }, "pager_address": "", "idle_timeout": {"option": "global"}, "roles": ["user"], "authorized_sites": ["heute"], "contactgroups": ["all"], "disable_notifications": {"disable": false}, "language": "de", "temperature_unit": "celsius", "interface_options": { "interface_theme": "dark" } "attr_1": "some_text", } C-: However, attempting to modify this user with the edit user endpoint PUT check_mk/api/v1/objects/user_config/user_1 C+: { "attr1": "edited_text" } C-: would fail and return a response like so C+: { "title": "Bad Request", "status": 400, "detail": "These fields have problems: _schema", "fields": { "_schema": [ "Unknown Attribute: 'attr_1'" ] } } C-: We now check for custom user attributes on the update endpoint and allow them if they exist, just like the create user endpoint.

7 months, 3 weeks

[2.2.0] Checkmk Werk 16002 created: veeam_cdp_jobs: Fix parsing of last sync which may contain floats like '123,456'

by Checkmk werks level 1

7 months, 3 weeks

[2.2.0] Checkmk Werk 15999 created: cisco_cpu_multiitem, cisco_fru_module_status: Fix parsing PhysicalClasses

by Checkmk werks level 1

7 months, 3 weeks

[2.3.0] Checkmk Werk 16137 adapted: user_config: allow update of custom user attributes

by Checkmk werks level 1

Werk 16137 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: user_config: allow update of custom user attributes Class: fix Compatible: incomp Component: rest-api Date: 1695731850 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This werk addresses an issue reported, where you could create a user with custom attributes, but you could not update the user's custom attributes. E.g. Calling this endpoint with the following payload would work, providing the custom attribute 'attr_1' exists. POST check_mk/api/v1/domain-types/user_config/collections/all C+: { "username": "user_1", "fullname": "user_1", "auth_option": { "auth_type": "password", "password": "password_with_at_least_12_characters" }, "disable_login": false, "contact_options": { "email": "user(a)example.com" }, "pager_address": "", "idle_timeout": {"option": "global"}, "roles": ["user"], "authorized_sites": ["heute"], "contactgroups": ["all"], "disable_notifications": {"disable": false}, "language": "de", "temperature_unit": "celsius", "interface_options": { "interface_theme": "dark" } "attr_1": "some_text", } C-: However, attempting to modify this user with the edit user endpoint PUT check_mk/api/v1/objects/user_config/user_1 C+: { "attr1": "edited_text" } C-: would fail and return a response like so C+: { "title": "Bad Request", "status": 400, "detail": "These fields have problems: _schema", "fields": { "_schema": [ "Unknown Attribute: 'attr_1'" ] } } C-: We now check for custom user attributes on the update endpoint and allow them if they exist, just like the create user endpoint. ------------------------------------<diff>------------------------------------------- Title: user_config: allow update of custom user attributes Class: fix Compatible: incomp Component: rest-api Date: 1695731850 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This werk addresses an issue reported, where you could create a user with custom attributes, but you could not update the user's custom attributes. E.g. Calling this endpoint with the following payload would work, providing the custom attribute 'attr_1' exists. POST check_mk/api/v1/domain-types/user_config/collections/all - ``` + C+: { "username": "user_1", "fullname": "user_1", "auth_option": { "auth_type": "password", "password": "password_with_at_least_12_characters" }, "disable_login": false, "contact_options": { "email": "user(a)example.com" }, "pager_address": "", "idle_timeout": {"option": "global"}, "roles": ["user"], "authorized_sites": ["heute"], "contactgroups": ["all"], "disable_notifications": {"disable": false}, "language": "de", "temperature_unit": "celsius", "interface_options": { "interface_theme": "dark" } "attr_1": "some_text", } - ``` + C-: However, attempting to modify this user with the edit user endpoint PUT check_mk/api/v1/objects/user_config/user_1 - ``` + C+: { "attr1": "edited_text" } - ``` + C-: would fail and return a response like so - ``` + C+: { "title": "Bad Request", "status": 400, "detail": "These fields have problems: _schema", "fields": { "_schema": [ "Unknown Attribute: 'attr_1'" ] } } - ``` + C-: We now check for custom user attributes on the update endpoint and allow them if they exist, just like the create user endpoint.

7 months, 3 weeks

[2.3.0] Checkmk Werk 16137 created: user_config: allow update of custom user attributes

by Checkmk werks level 1

Title: user_config: allow update of custom user attributes Class: fix Compatible: incomp Component: rest-api Date: 1695731850 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This werk addresses an issue reported, where you could create a user with custom attributes, but you could not update the user's custom attributes. E.g. Calling this endpoint with the following payload would work, providing the custom attribute 'attr_1' exists. POST check_mk/api/v1/domain-types/user_config/collections/all ``` { "username": "user_1", "fullname": "user_1", "auth_option": { "auth_type": "password", "password": "password_with_at_least_12_characters" }, "disable_login": false, "contact_options": { "email": "user(a)example.com" }, "pager_address": "", "idle_timeout": {"option": "global"}, "roles": ["user"], "authorized_sites": ["heute"], "contactgroups": ["all"], "disable_notifications": {"disable": false}, "language": "de", "temperature_unit": "celsius", "interface_options": { "interface_theme": "dark" } "attr_1": "some_text", } ``` However, attempting to modify this user with the edit user endpoint PUT check_mk/api/v1/objects/user_config/user_1 ``` { "attr1": "edited_text" } ``` would fail and return a response like so ``` { "title": "Bad Request", "status": 400, "detail": "These fields have problems: _schema", "fields": { "_schema": [ "Unknown Attribute: 'attr_1'" ] } } ``` We now check for custom user attributes on the update endpoint and allow them if they exist, just like the create user endpoint.

7 months, 3 weeks

[2.3.0] Checkmk Werk 16002 created: veeam_cdp_jobs: Fix parsing of last sync which may contain floats like '123,456'

by Checkmk werks level 1

7 months, 3 weeks

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2023