Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

[2.3.0] Checkmk Werk 15163 deleted: Add REMOVE_ACKNOWLEDGEMENT_BY_ID livestatus command

by Checkmk werks level 1

Werk 15163 was deleted. The following Werk is no longer relevant. Title: Add REMOVE_ACKNOWLEDGEMENT_BY_ID livestatus command Class: feature Compatible: compat Component: livestatus Date: 1689776576 Edition: cee Knowledge: undoc Level: 1 Version: 2.3.0b1 Use <tt>REMOVE_ACKNOWLEDGEMENT_BY_ID;[ID]\n</tt> to remove a single acknowledgement.

1 year

[2.3.0] Checkmk Werk 16140 created: Fix missing entries for Checkmk check helpers logger

by Checkmk werks level 1

Title: Fix missing entries for Checkmk check helpers logger Class: fix Compatible: compat Component: wato Date: 1695029015 Edition: cee Knowledge: doc Level: 1 State: unknown Version: 2.3.0b1 The log level setting to "Checkmk check helpers" under "Setup > General > Global settings > Logging of the core" would not always be taken into account, resulting in lost logging entries in cmc.log.

1 year

[2.3.0] Checkmk Werk 16103 created: dcd: phase 2.3 updating config now calling the update host endpoint with the correct data

by Checkmk werks level 1

Title: dcd: phase 2.3 updating config now calling the update host endpoint with the correct data Class: fix Compatible: compat Component: rest-api Date: 1694767693 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 Due to a recent change in the update_host rest-api endpoint, we inadvertently broke the dcd functionality. This werk addresses this issue by calling the update_host endpoint with the correct data format when performing the dcd step phase 2.3 updating config.

1 year

[2.3.0] Checkmk Werk 15165 created: Add two livestatus column: prediction_file and prediction_files

by Checkmk werks level 1

Title: Add two livestatus column: prediction_file and prediction_files Class: feature Compatible: compat Component: core Date: 1694757240 Edition: cre Knowledge: undoc Level: 1 Version: 2.3.0b1 Add two livestatus columns to the service table. The "prediction_files" column returns a list of files under "var/check_mk/prediction/HOST/SERVICE/". Example: <tt>lq 'GET services\nColumns: prediction_files\nFilter: description = Uptime'</tt> The "prediction_file" column is a dynamic column that returns the content of a file under "var/check_mk/prediction/HOST/SERVICE/" Example: <tt>lq 'GET services\nColumns: prediction_file:file:metric1/prediction1\nFilter: description = Uptime'</tt>

1 year

[2.1.0] Checkmk Werk 16079 created: cisco_temperature: Regression in temperature level evaluation

by Checkmk werks level 1

Title: cisco_temperature: Regression in temperature level evaluation Class: fix Compatible: compat Component: checks Date: 1693916294 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p34 This Werk fixes a regression that occured since Checkmk 2.1.0p31 and 2.2.0p8. In some cases, upper levels could be misinterpreted as lower levels, leading to false-positive <tt>WARN</tt> and <tt>CRIT</tt> states of <i>Temperature</i> services.

1 year

[2.2.0] Checkmk Werk 16079 created: cisco_temperature: Regression in temperature level evaluation

by Checkmk werks level 1

Title: cisco_temperature: Regression in temperature level evaluation Class: fix Compatible: compat Component: checks Date: 1693916294 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p10 This Werk fixes a regression that occured since Checkmk 2.1.0p31 and 2.2.0p8. In some cases, upper levels could be misinterpreted as lower levels, leading to false-positive <tt>WARN</tt> and <tt>CRIT</tt> states of <i>Temperature</i> services.

1 year

[2.2.0] Checkmk Werk 14211 created: Discard/Revert pending changes now shows a confirmation page instead of instant snapshot rollback

by Checkmk werks level 1

Title: Discard/Revert pending changes now shows a confirmation page instead of instant snapshot rollback Class: feature Compatible: compat Component: wato Date: 1694597619 Edition: cre Knowledge: undoc Level: 1 Version: 2.2.0p10 The confirmation page also shows changes which are already activated in the current configuration, but will be reverted once the latest snapshot is restored.

1 year

[2.3.0] Checkmk Werk 16100 created: licensing: the 'settings' field is now required for license configuration

by Checkmk werks level 1

Title: licensing: the 'settings' field is now required for license configuration Class: fix Compatible: incomp Component: rest-api Date: 1694687452 Edition: cre Knowledge: doc Level: 1 Version: 2.3.0b1 This werk addresses an issue found by our QA team with regards to the following endpoint PUT /domain-types/licensing/actions/configure/invoke Previously, we got an internal server error when attempting to call this endpoint with no 'settings' field or with no data for the 'settings' field. We have now made 'settings' a required field and the correct request data must be present. Examples of correct request data C+: { "settings": { "mode": "offline" } } C-: or C+: { "settings": { "mode": "online", "credentials": { "username": "application-account-id", "password": "application-account-password" }} } C-:

1 year

[2.1.0] Checkmk Werk 16099 created: create_host: creating a host with a custom attribute now returns expected attributes

by Checkmk werks level 1

Title: create_host: creating a host with a custom attribute now returns expected attributes Class: fix Compatible: compat Component: rest-api Date: 1694670257 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.1.0p34 This werk addresses an issue when creating a host with custom attributes. For example, when you added a new tag to a tag group and then created a host with that tag group: tag value, the created host would have this new attribute but it wouldn't have any other attributes. So sending this in your request, after creating the new tag 'tag1', C+: { "folder": "~", "host_name": "api_created_host2", "attributes": { "ipaddress": "127.0.0.1", "tag_agent": "no-agent", "tag_snmp_ds": "no-snmp", "tag_networking": "tag1" } } C-: before this would create a host with the only the tag networking attribute and ignore all others, like so C+: { ... "attributes" { "tag_networking": "tag1" } C-: Now, we return all the expected attributes.

1 year

[2.2.0] Checkmk Werk 16098 created: notification rules: match_folder value now matches correctly to available folders

by Checkmk werks level 1

Title: notification rules: match_folder value now matches correctly to available folders Class: fix Compatible: incomp Component: rest-api Date: 1694514118 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p10 This werk addresses an issue when creating or updating a notification rule via the REST-API. Previously, it would not correctly match the desired folder and as a result, you had to set this option to disabled which meant all rules were created in the main folder only. Now the match_folder value field should match a folder id, in the form of the folder path, replacing / for ~ E.g. /folder1 -> ~folder1 /folder1/folder2 -> ~folder1~folder2

1 year

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1