Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

Checkmk Werk 14613: Fix "Limit for upper bound dynamic levels" for predictive levels

by Checkmk werks level 1

ID: 14613 Title: Fix "Limit for upper bound dynamic levels" for predictive levels Component: Checks & agents Level: 1 Class: Bug fix Version: 2.0.0p39 You are affected by this change if you use the option "Limit for upper bound dynamic levels" for "Predictive Levels" for "CPU load". If the predictive levels predict a very low value, it's easy to overshoot those levels. Therefore the "Limit for upper bound dynamic levels" can define warn and crit levels which are used when the predictive values are below this defined warn and crit levels. The "CPU load" has a special mechanism that considers the number of CPUs, otherwise you would have to write special rules for servers with different number of CPU cores, as the load value is dependent on the number of cores. A high load for a 4 CPU computer may be a very low load for a 32 CPU computer. That's why checkmks' load values are divided by the number of CPUs to be able to define one rule for all your computers independent of the number of CPUs. The option "Limit for upper bound dynamic levels" did miss this adaption to the number of CPUs. This has been fixed and now the "Limit for upper bound dynamic levels" is internally multiplied by the number of CPUs. If you use the argument "Limit for upper bound dynamic levels" for "Predictive Levels" for "CPU load" and want to keep the current behaviour, you have to create different rules depending on the CPU count of your systems and divide the level entered by the number of CPUs. This is, of course not practical. We consider the old behaviour as not correct.

1 year, 1 month

Checkmk Werk 15985: AWS agent handles wafv2 rules with ByteMatchString correctly

by Checkmk werks level 1

ID: 15985 Title: AWS agent handles wafv2 rules with ByteMatchString correctly Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 When a wafv2 rule with the ByteMatchString was configured the agent would crash. In the debug output a message about an unserializable entry would appear. In the AWS UI you can configure a rule with ByteMatchString in any field using "Search string". This has been fixed now. No action required.

1 year, 1 month

Checkmk Werk 15260: Fixed rescheduling of non-existent service

by Checkmk werks level 1

ID: 15260 Title: Fixed rescheduling of non-existent service Component: Livestatus Level: 1 Class: Bug fix Version: 2.2.0p9 When a Livestatus query with a "WaitObject:" line for a non-existent service was sent to the monitoring core, a crash happened. This could e.g. be triggered by direct Livestatus queries or via a "Reschedule" in the GUI under certain circumstances. This was a regression in 2.2.0 and has been fixed.

1 year, 1 month

Checkmk Werk 15958: Custom extensions: Avoid duplicate graphs in the user interface due to `graph_info.append`

by Checkmk werks level 1

ID: 15958 Title: Custom extensions: Avoid duplicate graphs in the user interface due to `graph_info.append` Component: metrics Level: 1 Class: Bug fix Version: 2.2.0p8 This werk only concerns developers of custom Checkmk extensions. There are currently two ways for registering custom graph definitions: C+: graph_info["GRAPH_ID"] = GRAPH_DEFINITION C-: and C+: graph_info.append(GRAPH_DEFINITION) C-: Using the latter might have lead to duplicate graphs in the user interface. As of this werk, this is fixed.

1 year, 1 month

Checkmk Werk 15912: graylog_alerts: Fixed section parsing when transitioning from 2.1 to 2.2

by Checkmk werks level 1

ID: 15912 Title: graylog_alerts: Fixed section parsing when transitioning from 2.1 to 2.2 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 When transitioning from 2.1 to 2.2, parsing of the graylog alerts section used to fail. The error contains: C+: "exc_type": "AttributeError", "exc_value": "'list' object has no attribute 'get'" C-: This has now been fixed and the transition will not cause problems.

1 year, 1 month

Checkmk Werk 15291: aws: support for us-gov-* and cn-* regions

by Checkmk werks level 1

ID: 15291 Title: aws: support for us-gov-* and cn-* regions Component: agents Level: 1 Class: Bug fix Version: 2.3.0b1 The aws monitoring of checkmk differentiates between global and local services. For global services, and for getting an access token via sts service, checkmk assumed that the global region "us-east-1" can be used. This assumption is wrong. When hosting aws services in the following regions, you have to use said regions to access the global services: <ul> <li>us-gov-east-1</li> <li>us-gov-west-1</li> <li>cn-north-1</li> <li>cn-northwest-1</li> </ul> The error message visible in the debug output of the aws special agent was: C+: An error occurred (InvalidClientTokenId) when calling the GetCallerIdentity operation: The security token included in the request is invalid. C-: The global service region can now be configured.

1 year, 1 month

Checkmk Werk 16030: Alphabetic sorting for Kubernetes dashboard elements

by Checkmk werks level 1

ID: 16030 Title: Alphabetic sorting for Kubernetes dashboard elements Component: Multisite Level: 1 Class: New feature Version: 2.3.0b1 The elements of the cluster overview dashboard were not sorted at all previously. They are now sorted alphabetically. The sorting of the cluster and namespace dashboards was partially done on hostname, which leads to a sorting by namespace. To unify this behaviour, all list elements are now sorted by name alphabetically

1 year, 1 month

Checkmk Werk 15288: Remove HTMLGenerator.add_default_javascript function

by Checkmk werks level 1

ID: 15288 Title: Remove HTMLGenerator.add_default_javascript function Component: Setup Level: 1 Class: New feature Version: 2.3.0b1 MKPs that use custom javascript code may be affected by this change. A typical usage of this function may look like: C+: html.add_default_javascript("custom_id") C-: There is no 1:1 replacement for this call, but several ways to do similar things: C+: html.javascript("inlined_javascript_code();") C-: C+: html.javascript_file("browser/path/to_javascriptfile.js") C-:

1 year, 1 month

Checkmk Werk 15911: jenkins_jobs: Consider 'Override check state based on last build result' option

by Checkmk werks level 1

ID: 15911 Title: jenkins_jobs: Consider 'Override check state based on last build result' option Component: Checks & agents Level: 1 Class: Bug fix Version: 2.3.0b1 Previously, the check plugin did not consider the option 'Override check state based on last build result'. This led to wrong check states. This has now been fixed and the option will be considered as intended.

1 year, 1 month

Checkmk Werk 15151: azure_storageaccounts: Fix aggregation type and units in performance check

by Checkmk werks level 1

ID: 15151 Title: azure_storageaccounts: Fix aggregation type and units in performance check Component: Checks & agents Level: 1 Class: Bug fix Version: 2.0.0p39 There were several bugs in the Azure Storage performance check plugin. Success server latency and End-to-end server latency had no units in the service summary and showed wrong units in the metrics. The aggregation of all three metrics was wrong, total instead of avergage, which led to incorrect values being shown.

1 year, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1