[//]: # (werk v2)
# BI: Fixed incorrect aggregation of downtimes
key | value
---------- | ---
date | 2024-04-10T12:05:48+00:00
version | 2.3.0b6
class | fix
edition | cre
component | bi
level | 1
compatible | yes
The configuration option <tt>Escalate downtimes based on aggregated WARN state</tt> did not correctly since version 1.5.
The behaviour is now fixed and works like its mentioned in our [official documentation](https://docs.checkmk.com/latest/en/bi.html#_tuning_options)
[//]: # (werk v2)
# Valuespecs: Fixed confusion of values when ListOf contains another ListOf and all have the same magic
key | value
---------- | ---
date | 2024-04-10T09:56:58+00:00
version | 2.3.0b6
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Normally, ListOf elements embedded in other ListOf elements should contain a different magic value, otherwise errors will occur when processing forms.
This werk here allows the use of identical magic values.
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
either of the following conditions:
1. The monitoring is performed using an account without administrator rights.
2. Specific Oracle executable binaries — namely, <tt>sqlplus.exe</tt>,
<tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> - are not modifiable
by non-admin users.
If you are still unable to monitor Oracle, for example, you can't use an
unprivileged account for monitoring and changing of permission is not possible,
consider one of the following actions:
1. Enable <tt>Run as local group</tt> for group <tt>Administrators</tt> in
<tt>Run plugins and local checks using non-system account</tt> ruleset.
2. Adjust <tt>Oracle Binaries Permissions Check</tt> settings in <tt>ORACLE databases (Linux,
Solaris, AIX, Windows)</tt> ruleset.
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.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
? -
+ 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.
+ either of the following conditions:
+ 1. The monitoring is performed using an account without administrator rights.
+ 2. Specific Oracle executable binaries — namely, <tt>sqlplus.exe</tt>,
+ <tt>tnsping.exe</tt> and, if presented, <tt>crsctl.exe</tt> - are not modifiable
+ by non-admin users.
- 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.
+ If you are still unable to monitor Oracle, for example, you can't use an
+ unprivileged account for monitoring and changing of permission is not possible,
+ consider one of the following actions:
+ 1. Enable <tt>Run as local group</tt> for group <tt>Administrators</tt> in
+ <tt>Run plugins and local checks using non-system account</tt> ruleset.
+ 2. Adjust <tt>Oracle Binaries Permissions Check</tt> settings in <tt>ORACLE databases (Linux,
+ Solaris, AIX, Windows)</tt> ruleset.
More information about can be found at <a href="https://checkmk.atlassian.net/wiki/x/AQA1B">here</a>.
[//]: # (werk v2)
# winperf_if check correctly discovers and processes interfaces with spaces
key | value
---------- | ---
date | 2024-04-22T15:31:08+00:00
version | 2.3.0b7
class | fix
edition | cee
component | checks
level | 1
compatible | no
Previously, some Windows network interface names with additional spaces —
particularly before the hash symbol — were not recognized by the check engine.
This led to the absence of some services, especially Windows teaming network
interfaces.
In this release, such interface names are handled correctly thus fixing the
problem. Still, you may need to rediscover services again.
[//]: # (werk v2)
# inventory_primekey: do not crash upon empty node ID
key | value
---------- | ---
date | 2024-04-20T10:06:26+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
[//]: # (werk v2)
# Ignore empty "Multiple sites" filter if "Site" filter is set
key | value
---------- | ---
compatible | yes
version | 2.3.0b6
date | 2024-04-23T06:07:04+00:00
level | 1
class | fix
component | multisite
edition | cre
If both filters "Multiple sites" and "Sites" were set, the "Multiple sites"
filter was used, even if empty.
[//]: # (werk v2)
# Warn during update if contact groups are used in rulesets but not available
key | value
---------- | ---
date | 2024-04-23T07:42:11+00:00
version | 2.3.0b6
class | fix
edition | cme
component | wato
level | 1
compatible | yes
Some rulesets like 'Assignment of hosts (or services) to contact groups' use
contact groups which may not be synced because they are assigned to a specific
customer or to 'Provider' (default). This inconsistency might have already been
present in your configuration but went unnoticed in the previous versions. With
2.3, we introduced new validation mechanics which now warn you about this
potential issue.
With this change we make the shown error message a more helpful so that users
get a hint how to solve the situation.
[//]: # (werk v2)
# host_config: introduce include_links option for Show all hosts endpoint
key | value
---------- | ---
date | 2024-04-23T06:37:18+00:00
version | 2.3.0b6
class | feature
edition | cre
component | rest-api
level | 1
compatible | no
This werk introduces the flag 'include_links' for the 'Show all hosts'
host config endpoint. It toggles whether the links field should be populated
of the individual hosts. This serves as a mechanism to reduce the payload
generated. This field defaults to False and existing scripts therefore have
to be adjusted accordingly.
[//]: # (werk v2)
# mem_win: rename 'Commit Charge' to 'Virtual Memory' for correctness
key | value
---------- | ---
date | 2024-04-19T12:34:59+00:00
version | 2.3.0b6
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The value previously displayed as 'Commit Charge' did not match its
description. Therefore, this value has been accurately renamed to
'Virtual Memory,' while maintaining the original calculation method.
Correspondingly, the titles of related graphs have been adjusted to
reflect this change.
In versions prior to 2.3, the service summary included a metric labeled
'Pagefile installed.' This has now been correctly renamed to
'Total Virtual Memory,' as it never accurately represented the
'Pagefile installed.'