Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

Checkmk Werk 15983: time_period: verify time_period usage before deletion and fix the reference for time_periods being saved to the configuration file in exclude field.

by Checkmk werks level 1

ID: 15983 Title: time_period: verify time_period usage before deletion and fix the reference for time_periods being saved to the configuration file in exclude field. Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 Prior to this werk, the REST API did not correctly check if a time period to be deleted was being referenced by another object. This werk fixes this and prevents the REST API from deleting a time period that is currently being referenced. Also, prior to this werk, the REST API was incorrectly storing the reference to other time periods in the exlusion field. This werk fixes this and now the REST API stores the correct values in the configuration files.

1 year, 1 month

Checkmk Werk 15966: downtimes: add site property to the downtimes endpoints

by Checkmk werks level 1

ID: 15966 Title: downtimes: add site property to the downtimes endpoints Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 This werk introduces several changes to the downtimes endpoints. 1. Downtime IDs are integers beginning from 1, both for the main site & for remote sites. This means that the same downtime ID can exist on more than one site at the same time. This caused problems when calling the DELETE endpoint as we weren't sure which ID the client wanted to delete. To get around this problem, we have introduced a mandatory "site_id" field which the client has to specify when they want to delete a downtime. E.g. C+: curl \ --request POST \ --write-out "\nxxx-status_code=%{http_code}\n" \ --header "Authorization: Bearer $USERNAME $PASSWORD" \ --header "Accept: application/json" \ --header "Content-Type: application/json" \ --data '{ "delete_type": "params", "downtime_id": "1", "site_id": "heute" }' \ "$API_URL/domain-types/downtime/actions/delete/invoke" C-: 2. Like point 2, calling GET downtime with only a downtime ID could also cause the same problem. Therefore we have also introduced the mandatory "site_id" query parameter field here too. E.g. C+: curl \ -G \ --request GET \ --write-out "\nxxx-status_code=%{http_code}\n" \ --header "Authorization: Bearer $USERNAME $PASSWORD" \ --header "Accept: application/json" \ --data-urlencode 'site_id=heute' \ "$API_URL/objects/downtime/1" C-: 3. Now that the site_id field is mandatory in both the DELETE and GET downtime endpoints, we now return the site_id field as a downtime attribute in both the show downtime and show downtimes endpoints. 4. This last change introduces a new optional query parameter on the show all downtimes endpoint. The client can now specify the site_id as a filter, so that they can list all downtimes for a specific site. 5. We've added a response schema which adds to minor changes. a. The domainType for collection responses now correctly shows "downtime" instead of "dict" b. The API documentation now shows the expected response.

1 year, 1 month

Checkmk Werk 15982: time_period: Creation, modification or deletion of time periods from the API now adds entries to activate changes

by Checkmk werks level 1

ID: 15982 Title: time_period: Creation, modification or deletion of time periods from the API now adds entries to activate changes Component: REST API Level: 1 Class: Bug fix Version: 2.3.0b1 Before this werk, making modifications to time periods from the API did not add entries to activation changes. This werk fixes this behaviour and now the API generates the corresponding entries.

1 year, 1 month

Checkmk Werk 14858: Prevent event removal counted twice

by Checkmk werks level 1

ID: 14858 Title: Prevent event removal counted twice Component: Event Console Level: 1 Class: Bug fix Version: 2.1.0p32 A limit for Events did not work because the archive operation would count Event deletion twice. In some cases the number of Events would become negative which prevented the Event limit from doing it`s job. this was a regression introduced in 2.0.0p30 and 2.1.0p15

1 year, 1 month

Checkmk Werk 15164: Let host and service deletion cancel its downtime

by Checkmk werks level 1

ID: 15164 Title: Let host and service deletion cancel its downtime Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0p8 Activate change now cancels the downtime of vanished hosts and services.

1 year, 1 month

Checkmk Werk 16016: mk_postgres: addition of option to specify instance name

by Checkmk werks level 1

ID: 16016 Title: mk_postgres: addition of option to specify instance name Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0p8 The migration of the postgres_instances check plugin to the new CheckAPI broke the discovery mechanism of the plugin as it previously allowed an instance to have no specified name. This werk introduces the option to specify an explicit name for an instance. The mk_postgres plugin is adjusted accordingly and raises an error if the name cannot be inferred from .env file. To benefit from this change and also resolve the error, the user should adjust or bake the config file again and roll out the newly adapted plugin.

1 year, 1 month

Checkmk Werk 15971: Licensing: Missing license transfer in distributed setup

by Checkmk werks level 1

ID: 15971 Title: Licensing: Missing license transfer in distributed setup Component: Multisite Level: 1 Class: Bug fix Version: 2.3.0b1 Prior to this werk, the license of a central site in a distributed setup would not be transferred to remote sites if the remote site was in the "Free" license state, as this state is not allowed in distributed setups. This meant that remote sites could effectively not be licensed once they entered the "Free" state. Now the license information is distributed to all remote sites when the licensed verification is performed.

1 year, 1 month

Checkmk Werk 16021: Add support for Debian 12

by Checkmk werks level 1

ID: 16021 Title: Add support for Debian 12 Component: Site Management Level: 1 Class: New feature Version: 2.3.0b1 With this werk, Checkmk is build for Debian 12 Bookworm.

1 year, 1 month

Checkmk Werk 16020: Add support for Ubuntu 23.04

by Checkmk werks level 1

ID: 16020 Title: Add support for Ubuntu 23.04 Component: Site Management Level: 1 Class: New feature Version: 2.3.0b1 With this werk, Checkmk is build for Ubuntu 23.04 Lunar Lobster

1 year, 1 month

Checkmk Werk 15636: Predictive Levels: Show prediction if the value is 0

by Checkmk werks level 1

ID: 15636 Title: Predictive Levels: Show prediction if the value is 0 Component: Checks & agents Level: 2 Class: Bug fix Version: 2.3.0b1 Previously, the message C+: no reference for prediction yet C-: would be shown, if the prediction made by the CMC was <tt>0</tt>. With this Werk, the predicted value is now always shown. The prediction levels have been updated accordingly. LI: <tt>Absolute difference from prediction:</tt> 0 is treated like any other value. Some alarms, which used to be omitted, are now correctly reported. LI: <tt>In relation to standard deviation:</tt> 0 is treated like any other value. Some alarms, which used to be omitted, are now correctly reported. LI: <tt>Relative difference from prediction:</tt> Non-zero values are treated in a different manner. No dynamic levels are computed. This means the behaviour of this parameter has not changed with this Werk. Note, the configuration <tt>In relation to standard deviation</tt> can lead to false alarms, if the standard deviation is zero.

1 year, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1