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
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
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>.
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.
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.
[//]: # (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.
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.
[//]: # (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.
[//]: # (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.
[//]: # (werk v2)
# Crash on activate changes when re-registering agents
key | value
---------- | ---
date | 2024-03-28T15:50:10+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When re-registering agents, a call to activate changes could crash with an error message like
```
[Errno 2] No such file or directory: '/omd/sites/<site>/var/agent-receiver/received-outputs/<uuid>
```