Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Unusable services for "HPE Proliant Servers: Raid Status"
key | value
--- | ---
compatible | no
version | 2.3.0b1
date | 2023-12-15T10:35:33+00:00
level | 1
class | fix
component | checks
edition | cre
This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin.
This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade.
In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below.
We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`).
Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like.
We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero').
As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions.
If this affects you, you might also want to fix the services in the monitoring history by running
```
sed -i 's|\\x00|\\\\x00|' var/check_mk/core/history var/check_mk/core/archive/*
```
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Unusable services for "HPE Proliant Servers: Raid Status"
key | value
--- | ---
compatible | no
version | 2.3.0b1
date | 2023-12-15T10:35:33+00:00
level | 1
class | fix
component | checks
edition | cre
This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin.
This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade.
In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below.
We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`).
Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like.
We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero').
As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions.
If this affects you, you might also want to fix the services in the monitoring history by running
```
- sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/*
+ sed -i 's|\\x00|\\\\x00|' var/check_mk/core/history var/check_mk/core/archive/*
? + ++
```
[//]: # (werk v2)
# APACHE_TCP_ADDR now allows IPv6 address
key | value
---------- | ---
date | 2024-04-22T11:05:16+00:00
version | 2.3.0p1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
Previously, using the command `omd config set APACHE_TCP_ADDR` with a IPv6 address would fail. For
example, the command
```
$ omd config set APACHE_TCP_ADDR "[::]"
```
resulted in `Invalid value for '[::]'. Does not match allowed pattern.`
With this Werk, it `omd` only checks that a `Listen` directive for Apache can be constructed from the
`APACHE_TCP_ADDR`. In particular, this a IPv6 address can be configured. Such an address must be
surrounded by square brackets.
[//]: # (werk v2)
# reports: remove site_id of other customers when rendering reports
key | value
---------- | ---
date | 2024-04-18T07:21:06+00:00
version | 2.3.0b7
class | fix
edition | cme
component | reporting
level | 1
compatible | yes
When you try to create a report and a remote site is not reachable, the
report will include the site_id of said site. This werk addresses this
issue by only showing errors that belong to that customer.
[//]: # (werk v2)
# "checkgroup_parameters:if": Rename to "checkgroup_parameters:interfaces"
key | value
---------- | ---
date | 2024-04-26T11:27:20+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | no
This only affects you if you are configuring rules through the REST API.
In order to make the "checkgroup_parameters:if" ruleset compliant with the new Ruleset API, it has been renamed to "checkgroup_parameters:interfaces".
Any configuration inside Checkmk will be automatically updated, however any outside references to the old name will have to be adjusted manually.
Werk 16807 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ignore unknown "Disabled checks" during update config
key | value
---------- | ---
date | 2024-04-24T12:25:30+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like
```
WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: ,
-| Rule nr: 1, Exception: ifoperstatus is not an allowed value)
```
These invalid values are ignored now.
They do no harm and they are dropped upon editing the rule.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ignore unknown "Disabled checks" during update config
key | value
---------- | ---
date | 2024-04-24T12:25:30+00:00
- version | 2.3.0b7
? ^^
+ version | 2.3.0p1
? ^^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like
```
WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: ,
-| Rule nr: 1, Exception: ifoperstatus is not an allowed value)
```
These invalid values are ignored now.
They do no harm and they are dropped upon editing the rule.
Werk 16811 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Performance regression during config generation in 2.3.0b6
key | value
---------- | ---
date | 2024-04-26T08:27:28+00:00
version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a performance regression introduced in Checkmk version 2.3.0b6.
The introduced issue slowed the config generation down proportional to the
number of monitored hosts.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Performance regression during config generation in 2.3.0b6
key | value
---------- | ---
date | 2024-04-26T08:27:28+00:00
- version | 2.3.0p1
? --
+ version | 2.3.0
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a performance regression introduced in Checkmk version 2.3.0b6.
The introduced issue slowed the config generation down proportional to the
number of monitored hosts.
[//]: # (werk v2)
# Performance regression during config generation in 2.3.0b6
key | value
---------- | ---
date | 2024-04-26T08:27:28+00:00
version | 2.3.0p1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a performance regression introduced in Checkmk version 2.3.0b6.
The introduced issue slowed the config generation down proportional to the
number of monitored hosts.
Werk 15842 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Enhanced MS SQL Server monitoring
key | value
---------- | ---
date | 2024-04-03T07:47:56+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | yes
With this release MS SQL Server is monitored using new plugin and new GUI.
The old plugin is still supported but are considered deprecated.
Key Enhancements out-of-the-box:
- Configuration flexibility: The plugin can be configured through a YAML config file for any edition and/or a graphical user interface (GUI) for enterprise edition or better.
- Cross platform: The plugin can be deployed on Linux and Windows.
- Enhanced monitoring capabilities: Supports monitoring of remote databases on both Linux and Windows hosts, in addition to local monitoring on Windows hosts.
- Customizable monitoring sections: Sections are now selectable and configurable
- Customizable SQL statements: you may change SQL statement either manually(place file in `mssql` sub directory in config dir) or using `Custom files` rule in GUI.
- Multi-instance support: Enables the selection of different instances for monitoring. Every instance can be configured separately
- Multi-host support: possible to monitor databases on various hosts using one deployed plugin.
- Security enhancements: Limited support for certificates is now available.
- Asynchronous operation: Any section with exception `instances` can be set up for asynchronous operation.
- Piggyback: It's possible to direct the output of a plugin to a different host, rather than to the host that retrieves the data.
- Other improvements:
- Automatic detection of instances is possible for any Windows host, local and remote, depending on SQL Server Setup.
- Full logging support including rotation and file limits
- Limit for maximal connection counts
- Cache time and timeout can be configured too
With regard to the old plug-in, there are also a few restrictions at the moment:
- The database instances must be accessible via TCP/IP.
- If several databases are running on a system, each using their own IP addresses, these must be explicitly specified in the configuration of the agent plug-in, as the addresses and ports are currently not yet found automatically.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Enhanced MS SQL Server monitoring
key | value
---------- | ---
date | 2024-04-03T07:47:56+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 2
compatible | yes
With this release MS SQL Server is monitored using new plugin and new GUI.
The old plugin is still supported but are considered deprecated.
Key Enhancements out-of-the-box:
- Configuration flexibility: The plugin can be configured through a YAML config file for any edition and/or a graphical user interface (GUI) for enterprise edition or better.
- Cross platform: The plugin can be deployed on Linux and Windows.
- Enhanced monitoring capabilities: Supports monitoring of remote databases on both Linux and Windows hosts, in addition to local monitoring on Windows hosts.
- Customizable monitoring sections: Sections are now selectable and configurable
- Customizable SQL statements: you may change SQL statement either manually(place file in `mssql` sub directory in config dir) or using `Custom files` rule in GUI.
- Multi-instance support: Enables the selection of different instances for monitoring. Every instance can be configured separately
- Multi-host support: possible to monitor databases on various hosts using one deployed plugin.
- Security enhancements: Limited support for certificates is now available.
- Asynchronous operation: Any section with exception `instances` can be set up for asynchronous operation.
- Piggyback: It's possible to direct the output of a plugin to a different host, rather than to the host that retrieves the data.
- Other improvements:
- Automatic detection of instances is possible for any Windows host, local and remote, depending on SQL Server Setup.
- Full logging support including rotation and file limits
- Limit for maximal connection counts
- Cache time and timeout can be configured too
-
+ With regard to the old plug-in, there are also a few restrictions at the moment:
+ - The database instances must be accessible via TCP/IP.
+ - If several databases are running on a system, each using their own IP addresses, these must be explicitly specified in the configuration of the agent plug-in, as the addresses and ports are currently not yet found automatically.