Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15936 discussions

[2.2.0] Checkmk Werk 16493 adapted: netapp_ontap_snapvault: improves lagtime calculation

by Checkmk werks level 1

Werk 16493 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: netapp_ontap_snapvault: improves lagtime calculation Class: fix Compatible: compat Component: checks Date: 1708076378 Edition: cre Level: 1 Version: 2.2.0p23 ------------------------------------<diff>------------------------------------------- Title: netapp_ontap_snapvault: improves lagtime calculation Class: fix Compatible: compat Component: checks Date: 1708076378 Edition: cre Level: 1 Version: 2.2.0p23 - With this new type of calculation, since we don't have a reference for when this lagtime started or ended, - we always consider a month to be made up of 30 days.

7 months

[2.2.0] Checkmk Werk 16493 created: netapp_ontap_snapvault: improves lagtime calculation

by Checkmk werks level 1

Title: netapp_ontap_snapvault: improves lagtime calculation Class: fix Compatible: compat Component: checks Date: 1708076378 Edition: cre Level: 1 Version: 2.2.0p23 With this new type of calculation, since we don't have a reference for when this lagtime started or ended, we always consider a month to be made up of 30 days.

7 months

[2.2.0] Checkmk Werk 16506 created: aws: Inventorization of EC2 and ELB tags as host labels

by Checkmk werks level 1

Title: aws: Inventorization of EC2 and ELB tags as host labels Class: fix Compatible: compat Component: checks Date: 1708516567 Edition: cre Level: 1 Version: 2.2.0p23 There was a problem during service discovery which prevented Checkmk from assigning the AWS EC2 and ELB tags delivered by the AWS agent to their respective piggyback hosts. This werk fixes the discovery process such that the data is parsed properly and custom tags from AWS will now show up as host labels on the created piggyback hosts.

7 months

[2.4.0] Checkmk Werk 16371 created: sla: range field for predefined_time_range parameter is mandatory

by Checkmk werks level 1

[//]: # (werk v2) # sla: range field for predefined_time_range parameter is mandatory key | value ---------- | --- date | 2024-02-23T08:00:57+00:00 version | 2.4.0b1 class | fix edition | cee component | rest-api level | 1 compatible | yes Before this werk, when the sla was computed for a predefined time range without specifying the range field, an error status 500 Internal Server Error was returned. This werk solves the problem by checking for the existence of the range field, and if it does not exist, the endpoint returns an error status 400 - Bad Request.

7 months

[2.4.0] Checkmk Werk 16492 created: netapp_ontap_info: enhanced presentation of NetApp system information

by Checkmk werks level 1

[//]: # (werk v2) # netapp_ontap_info: enhanced presentation of NetApp system information key | value ---------- | --- date | 2024-02-15T10:04:03+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The version and hardware information for a NetApp system was only displayed for the first retrieved node. With this werk we now display information for each retrieved node.

7 months

[2.4.0] Checkmk Werk 16521 created: bi_rule: schema update to match the api docs

by Checkmk werks level 1

[//]: # (werk v2) # bi_rule: schema update to match the api docs key | value ---------- | --- date | 2024-02-19T14:34:33+00:00 version | 2.4.0b1 class | fix edition | cre component | rest-api level | 1 compatible | no The Open API schema previously did not reflect the response or the request schema format that was required to create or show BI rules. This werk addresses this issue. Previously, when creating or getting a BI rule, via the REST-API, the schema for host_label_groups or service_label_groups looked similar to the following: ``` "host_label_groups": [ [ "and", [ ["and", "mystery/switch:yes"], ["or", "mystery/switch:no"], ], ], ] ``` This did not match the schema documented in the Open API docs. To fix this, we have now changed the format to the following ``` "host_label_groups": [ { "operator": "and", "label_group": [ {"operator": "and", "label": "mystery/switch:yes"}, {"operator": "or", "label": "mystery/switch:no"}, ], }, ] ``` This also aligns with other endpoints that use our new host_label_groups or service_label_groups, for example the rules endpoints. As this is a breaking change, user scripts should be adjusted accordingly.

7 months

[2.4.0] Checkmk Werk 16171 created: aws: Fix Cloudwatch alarms fetching

by Checkmk werks level 1

[//]: # (werk v2) # aws: Fix Cloudwatch alarms fetching key | value ---------- | --- compatible | yes version | 2.4.0b1 date | 2024-02-21T13:16:55+00:00 level | 1 class | fix component | checks edition | cre Cloudwatch alarms weren't fetched properly for environments with a lot of alarms. It resulted in missing alarms in the 'AWS/CloudWatch Alarms' service.

7 months

[2.2.0] Checkmk Werk 16236 created: Regression when obtaining mails from mailbox

by Checkmk werks level 1

Title: Regression when obtaining mails from mailbox Class: fix Compatible: compat Component: checks Date: 1708521462 Edition: cre Level: 1 Version: 2.2.0p23 This regression exists since 2.2.0b1. Monitoring mails in your in box may have not been possible. This is fixed now.

7 months, 1 week

[2.2.0] Checkmk Werk 16479 created: ntopng integration: fix ntopng version 6.0+ compatibility

by Checkmk werks level 1

Title: ntopng integration: fix ntopng version 6.0+ compatibility Class: fix Compatible: compat Component: ntopng_integration Date: 1708510081 Edition: cee Level: 1 Version: 2.2.0p23 The ntopng integration is now compatible with ntopng versions newer than 6.0.

7 months, 1 week

[2.3.0] Checkmk Werk 16236 created: Regression when obtaining mails from mailbox

by Checkmk werks level 1

[//]: # (werk v2) # Regression when obtaining mails from mailbox key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2024-02-21T13:17:42+00:00 level | 1 class | fix component | checks edition | cre This regression exists since 2.2.0b1. Monitoring mails in your in box may have not been possible. This is fixed now.

7 months, 1 week

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1