[//]: # (werk v2)
# mcafee_webgateway: base OID changed
key | value
---------- | ---
date | 2024-03-19T07:49:40+00:00
version | 2.3.0b5
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The McAfee Web Gateway has been rebranded to Skyhigh Secure Web Gateway with its release 12.2.2.
The base OID has been changed from `.1.3.6.1.4.1.1230*` to `.1.3.6.1.4.1.59732*`.
Where possibile the "McAfee" string has been removed in favor of more generic therms.
The old plugin names and ruleset names have been kept for compatibility/history-keeping reasons.
[//]: # (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
[//]: # (werk v2)
# RabbitMQ: extend help text for instance name with macro option
key | value
---------- | ---
date | 2024-02-12T09:09:37+00:00
version | 2.3.0b4
class | feature
edition | cre
component | wato
level | 1
compatible | yes
[//]: # (werk v2)
# bluenet: allow discovery for newer devices
key | value
---------- | ---
date | 2024-02-12T12:20:21+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Prior to this werk, the snmp detect condition was too
restrictive which excluded subsequently new devices.
Those new devices had another oid section following the
initial condition. This werk makes the detect condition
more lenient to allow discovery of those devices.
[//]: # (werk v2)
# Bulk host rename: loosen requirements for adding prefixes and suffixes
key | value
---------- | ---
date | 2024-03-25T07:55:46+00:00
version | 2.3.0b4
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When bulk renaming hosts the "Add Prefix" and "Add Suffix" options only allowed
valid hostnames. This requirement was now changed, so that only the resulting
hostname is validated.
[//]: # (werk v2)
# jolokia_metrics: fix monitoring of tomcat requestCount metric
key | value
---------- | ---
date | 2024-03-27T17:14:30+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The `requestCount` metric for tomcat servers was calculated by the plugin to obtain the number of requests per second;
but the value obtained by the special agent is already in that format.
It is therefore sufficient to monitor the value without further processing.
[//]: # (werk v2)
# Make scp command work as site userr on SLES 15
key | value
---------- | ---
date | 2024-03-28T08:38:12+00:00
version | 2.3.0b4
class | fix
edition | cre
component | omd
level | 1
compatible | yes
On SUSE Linux Enterprise Server 15 systems, the `scp` command could crash with
```
/usr/bin/ssh: symbol lookup error: /usr/bin/ssh: undefined symbol: EVP_KDF_CTX_free, version OPENSSL_1_1_1d lost connection
```
when executed as a site user.
Werk 16414 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Migrate Old Configuration Format For 'Disable notifications'
key | value
---------- | ---
date | 2024-03-18T13:59:16+00:00
version | 2.3.0b4
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
In Werk #6417, we announced that some changes to `etc/check_mk/conf.d/wato/contacts.mk` are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
```
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
```
With this Werk, the configuration is migrated automatically.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Support Old Configuration Format For 'Disable notifications'
? ^^^^^
+ # Migrate Old Configuration Format For 'Disable notifications'
? ^^^ + +
key | value
---------- | ---
date | 2024-03-18T13:59:16+00:00
version | 2.3.0b4
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
In Werk #6417, we announced that some changes to `etc/check_mk/conf.d/wato/contacts.mk` are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
```
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
```
- This crash is now no longer shown.
+ With this Werk, the configuration is migrated automatically.
[//]: # (werk v2)
# Support Old Configuration Format For 'Disable notifications'
key | value
---------- | ---
date | 2024-03-18T13:59:16+00:00
version | 2.3.0b4
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
In Werk #6417, we announced that some changes to `etc/check_mk/conf.d/wato/contacts.mk` are
necessary before updating. In case a user did not migrate his configuration, they would encounter
the following crash in 2.2.0, but not in 2.1.0:
```
File "/omd/sites/edding/lib/python3/cmk/base/notify.py", line 968, in rbn_rule_contacts
if disable_notifications_opts.get("disable", False):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'get'
```
This crash is now no longer shown.