Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.3.0] Checkmk Werk 16605 adapted: check_wmi_webservices: fix CurrentConnections monitoring

by Checkmk werks level 1

Werk 16605 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # check_wmi_webservices: fix CurrentConnections monitoring key | value ---------- | --- date | 2024-04-02T06:44:07+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | yes The CurrentConnections metric was calculated "per second". We now directly show the number of connections returned by the service. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # check_wmi_webservices: fix CurrentConnections monitoring key | value ---------- | --- date | 2024-04-02T06:44:07+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes The CurrentConnections metric was calculated "per second". We now directly show the number of connections returned by the service.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16652 adapted: NVIDIA Graphics Card: Fix parsing error on new data format

by Checkmk werks level 1

Werk 16652 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # NVIDIA Graphics Card: Fix parsing error on new data format key | value ---------- | --- date | 2024-04-05T10:17:08+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | yes ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # NVIDIA Graphics Card: Fix parsing error on new data format key | value ---------- | --- date | 2024-04-05T10:17:08+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16675 adapted: Ruleset API: Remove unused evaluation type specification

by Checkmk werks level 1

Werk 16675 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ruleset API: Remove unused evaluation type specification key | value ---------- | --- date | 2024-04-04T10:58:02+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | no This change is only relevant for plugin developers. Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other. However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type. For the affected rule specs this option was removed: * AgentConfig * NotificationParameters * DiscoveryParameters ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ruleset API: Remove unused evaluation type specification key | value ---------- | --- date | 2024-04-04T10:58:02+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | checks level | 1 compatible | no This change is only relevant for plugin developers. Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other. However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type. For the affected rule specs this option was removed: * AgentConfig * NotificationParameters * DiscoveryParameters

3 months, 3 weeks

[2.3.0] Checkmk Werk 15843 adapted: mk_oracle(ps1): Follow-up to privilege escalation fix

by Checkmk werks level 1

Werk 15843 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no version | 2.3.0b4 date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. Since this release, Oracle monitoring on Windows is fully supported under condition you use an account without administrator rights or the certain executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> are write-protected, with the possible exception being the Administrator. If you are unable or prefer not to use an unprivileged account then you may need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>, <tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator user and group. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # mk_oracle(ps1): Follow-up to privilege escalation fix key | value ---------- | --- compatible | no - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ date | 2024-04-05T11:02:27+00:00 level | 2 class | fix component | checks edition | cre You might be affected by this Werk if you use <tt>mk_oracle</tt> on Windows. Werk <a href="https://checkmk.com/werk/16232">Werk #16232</a> introduced a regression, thereby disrupting Oracle monitoring on Windows. This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4. Since this release, Oracle monitoring on Windows is fully supported under condition you use an account without administrator rights or the certain executable binaries, <tt>sqlplus.exe</tt>, <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> are write-protected, with the possible exception being the Administrator. If you are unable or prefer not to use an unprivileged account then you may need to adjust permissions for above mentioned binaries: remove <tt>Write</tt>, <tt>Full Control</tt> and <tt>Modify</tt> permissions for any non-Administrator user and group. More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16580 adapted: Dashboard: Fix event statistics not displaying information if no events found

by Checkmk werks level 1

Werk 16580 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Dashboard: Fix event statistics not displaying information if no events found key | value ---------- | --- date | 2024-03-20T10:34:20+00:00 version | 2.3.0b4 class | fix edition | cre component | multisite level | 1 compatible | yes Prior to this Werk, if no events were found, the event statistics dashlet was drawn empty. This Werk corrects that behaviour and if no events are found, the graph should show with a count of zero. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Dashboard: Fix event statistics not displaying information if no events found key | value ---------- | --- date | 2024-03-20T10:34:20+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | multisite level | 1 compatible | yes Prior to this Werk, if no events were found, the event statistics dashlet was drawn empty. This Werk corrects that behaviour and if no events are found, the graph should show with a count of zero.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16627 adapted: kube_persistent_volume_claim: resolve KeyError crash when Volume parameters are configured

by Checkmk werks level 1

Werk 16627 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # kube_persistent_volume_claim: resolve KeyError crash when Volume parameters are configured key | value ---------- | --- date | 2024-04-03T10:30:30+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | yes Before this update, configuring 'Volume parameters' in the PVC check plugin led to a crash. This issue arose because the plugin was not designed to process trend size-related levels, which, however, were anticipated by the general filesystem function handler shared among filesystem-related check plugins. To resolve this, the general function has been modified to bypass trend computation when a trend rule is not set, a scenario always applicable to the PVC check plugin. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # kube_persistent_volume_claim: resolve KeyError crash when Volume parameters are configured key | value ---------- | --- date | 2024-04-03T10:30:30+00:00 - version | 2.3.0b5 ? ^ + version | 2.3.0b4 ? ^ class | fix edition | cre component | checks level | 1 compatible | yes Before this update, configuring 'Volume parameters' in the PVC check plugin led to a crash. This issue arose because the plugin was not designed to process trend size-related levels, which, however, were anticipated by the general filesystem function handler shared among filesystem-related check plugins. To resolve this, the general function has been modified to bypass trend computation when a trend rule is not set, a scenario always applicable to the PVC check plugin.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16677 created: Ruleset API: Rename PredictiveLevels.prefill_stddev_diff to prefill_stdev_diff

by Checkmk werks level 1

[//]: # (werk v2) # Ruleset API: Rename PredictiveLevels.prefill_stddev_diff to prefill_stdev_diff key | value ---------- | --- date | 2024-04-08T14:16:32+00:00 version | 2.3.0b5 class | fix edition | cre component | checks level | 1 compatible | no This change is only relevant for plugin developers.

3 months, 3 weeks

[2.3.0] Checkmk Werk 15515 adapted: check_http: Soft deprecatation of old HTTP monitoring plug-in

by Checkmk werks level 1

Werk 15515 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # check_http: Soft deprecatation of old HTTP monitoring plug-in key | value ---------- | --- date | 2024-04-03T13:15:48+00:00 version | 2.3.0b4 class | feature edition | cre component | checks level | 2 compatible | no The old plug-in is being deprecated in a soft way with this werk. Unlike hard deprecation, the deprecated rule set "Check HTTP service" will remain fully functional. However, new rules should only be created if absolutely necessary, such as when experiencing issues with the new "Check HTTP web service" implementation and needing to roll back to the old one. Please note that the rule set will be hard deprecated in version 2.4.0, meaning that you will no longer be able to create new rules. However, the plug-in itself will remain available as this is a component of the monitoring-plugins collection that comes with Checkmk. Please let us know if you find any features that were present in the old plug-in but are missing in the new one. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # check_http: Soft deprecatation of old HTTP monitoring plug-in key | value ---------- | --- date | 2024-04-03T13:15:48+00:00 version | 2.3.0b4 class | feature edition | cre component | checks level | 2 compatible | no The old plug-in is being deprecated in a soft way with this werk. Unlike hard deprecation, the deprecated rule set "Check HTTP service" will remain fully functional. However, new rules should only be created if absolutely necessary, such as when experiencing issues with the new "Check HTTP web service" implementation and needing to roll back to the old one. Please note that the rule set will be hard deprecated in version 2.4.0, meaning that you will no longer be able to create new rules. However, the plug-in itself will remain available as this is a component of the monitoring-plugins collection that comes with Checkmk. - Please know us know if you find any features that were present in the old ? -------- + Please let us know if you find any features that were present in the old ? +++++++ plug-in but are missing in the new one.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16420 created: jolokia_info: Support Version 2.0

by Checkmk werks level 1

[//]: # (werk v2) # jolokia_info: Support Version 2.0 key | value ---------- | --- date | 2024-04-08T09:28:55+00:00 version | 2.3.0b5 class | feature edition | cre component | checks level | 1 compatible | yes Jolokia 2.0 was released 2023-12-19. With the release some changes to the Jolokia Protocol have been introduced. If a user installed this version of Jolokia, the check plugin `jolokia_info` showed `unknown` instead of the product information. After updating the agent plugin `mk_jolokia.py`, the correct information will be shown again.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16615 created: Remove websphere_mq plugin

by Checkmk werks level 1

[//]: # (werk v2) # Remove websphere_mq plugin key | value ---------- | --- date | 2024-03-11T11:09:48+00:00 version | 2.3.0b5 class | security edition | cre component | checks level | 1 compatible | yes With this Werk the `websphere_mq` plugin is removed for security reasons. In this plugin the output of `ps` is used to determine an argument for `runmqsc`. This meant that anybody who can launch processes with an arbitrary command line could manipulate one argument to `runmqsc`. The plugin was already superseded by the agent plugin `ibm_mq` and deprecated with Werk [10752](https://checkmk.com/werk/10752) and version 2.0.0. Since this plugin is already deprecated and it was not configurable via the *agent bakery* we assumed that this plugin is not frequently used. Therefore we decided to not fix the issue but to push the removal. We found this vulnerability internally. __Affected versions__: * 2.3.0 * 2.2.0 * 2.1.0 * 2.0.0 __Mitigations__: Migrate to the `ibm_mq` plugin. __Vulnerability Management__: We have rated the issue with a CVSS Score of 6.5 (Medium) with the following CVSS vector: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`. We assigned CVE-2024-3367 to this vulnerability. __Changes__: The plugin was removed.

3 months, 3 weeks

← Newer
1
...
21
22
23
24
25
26
27
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024