[//]: # (werk v2)
# Import Azure tags as service labels
key | value
---------- | ---
date | 2024-01-29T07:26:41+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
Azure resource tags are now imported as service labels as well. Each service that is discovered for an Azure resource now holds the resource's tags as service labels.
Also, you can now restrict the import of Azure tags via regex or disable the import altogether. This can be done in the rule "Microsoft Azure" via option "Import tags as host/service labels".
Note that tags are validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So an Azure resource tag "tag:key":"" will now be shown as "tag_key":"true".
[//]: # (werk v2)
# Changed host labels for Azure Resource Groups and Virutal Machines
key | value
---------- | ---
date | 2024-01-26T12:20:23+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | no
This werk affects users who use the tags of Azure Resource Groups or Virtual Machines (if monitored as hosts) as host labels in Checkmk.
The host labels are renamed from the original Azure format "{key}":"{value}" to "cmk/azure/tag/{key}":"{value}" in order to stay consistent with other host labels and to avoid overwriting existing Checkmk labels.
Additionally, label keys and values are now validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So a former label "label:key":"" will now be shown as "label_key":"true".
The old labels will be removed in version 2.4.0.
[//]: # (werk v2)
# if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description
key | value
---------- | ---
date | 2024-02-01T16:48:01+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
Sometimes the Lancom routers don't provide a name. During data parsing this caused the description to be left as an empty string.
As a result of that, when the router description was configured to be used for the Service Desciption, the discovery did not work properly.
This has now been fixed by having a fallback mechanism. If the router name is not present, the router description will be used.
Because of the change, the user is required to execute the service discovery again in order to discover any new services.
As well as get rid of any vanished services.
[//]: # (werk v2)
# omd start mkeventd: Error Code of Event Daemon
key | value
---------- | ---
date | 2024-02-02T12:32:48+00:00
version | 2.3.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
The command `omd start mkeventd` starts the event daemon. Previously, any exit code produced
by this daemon would be ignored. Now, if the exit code is non-zero, then the message `Failed` is
shown and the command `omd start mkeventd` exits with error code 2.
[//]: # (werk v2)
# Hide private topics in dropdowns
key | value
---------- | ---
date | 2024-02-01T08:07:44+00:00
version | 2.3.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Private topics were showing up in dropdowns (e.g. when editing dashboards).
Now they are hidden if the user does not have permissions for them.
[//]: # (werk v2)
# Fix topics being falsely shown as public
key | value
---------- | ---
date | 2024-02-01T08:01:39+00:00
version | 2.3.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | no
Previously, pagetypes (bookmarks, custom graphs, topics etc.) were falsely
handled as public, rather than private. Items published only to specific groups
are not affected and were handled correctly.
This change may cause users to no longer see public overwrites by admins for
example. Please ensure your permissions and publish states are configured
correctly.
[//]: # (werk v2)
# netapp_ontap_environment: show unit of measurement in summary
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-01T13:34:16+00:00
level | 1
class | fix
component | checks
edition | cre
The service summary now displays the units of measurement of the monitored value.
Werk 16295 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: postfix_mailq_status: Rework discovery
Class: fix
Compatible: compat
Component: checks
Date: 1700560692
Edition: cre
Level: 1
Version: 2.3.0b1
With this werk the postfix status service is not discovered if Postfix is not running.
The default mail queue is now discovered as "Postfix Status default".
------------------------------------<diff>-------------------------------------------
Title: postfix_mailq_status: Rework discovery
Class: fix
- Compatible: incomp
? --
+ Compatible: compat
? ++
Component: checks
Date: 1700560692
Edition: cre
Level: 1
Version: 2.3.0b1
With this werk the postfix status service is not discovered if Postfix is not running.
The default mail queue is now discovered as "Postfix Status default".
- In order to make the check plugin work you have to perform a re-discovery on the affected hosts.
- Otherwise, the service "Postfix Status" (dicovered before this change) will stop working.
-
[//]: # (werk v2)
# postfix_mailq: Rename "Postfix Queue" to "Postfix Queue default"
key | value
---------- | ---
date | 2024-02-01T08:44:18+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This affects users monitoring hosts that run one single postfix instance.
For new installations, the service "Postfix Queue" will be renamed to "Postfix Queue default".
In general, Checkmk is able to monitor multiple postfix instances running on the monitored host.
This will change the name in the common case where users are not running multiple postfix instances, but only the "default" one.
If you want to switch to the new service description after an upgrade, you can do so using the setting "Use new service descriptions".
Be aware that you will lose the historic data in case you do that.
Werk 15694 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Remove mod_auth_mellon
Class: feature
Compatible: incomp
Component: omd
Date: 1693380015
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.3.0b1
With Checkmk 2.2, announced by Werk #14977, the usage of mod_auth_mellon was deprecated. This release now removes mod_auth_mellon.
If you still have mod_auth_mellon in your apache config, the apache service will not be able to start.
Errors are logged to <tt>var/log/apache2/error_log</tt>.
If you want to continue to use SAML you can do it in the Enterprise Edition via <i>Setup -> Users -> SAML connections</i>.
------------------------------------<diff>-------------------------------------------
Title: Remove mod_auth_mellon
Class: feature
Compatible: incomp
Component: omd
Date: 1693380015
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.3.0b1
With Checkmk 2.2, announced by Werk #14977, the usage of mod_auth_mellon was deprecated. This release now removes mod_auth_mellon.
If you still have mod_auth_mellon in your apache config, the apache service will not be able to start.
- Errors are logged to <tt>var/lib/apache2/error_log</tt>.
? ^^
+ Errors are logged to <tt>var/log/apache2/error_log</tt>.
? ^^
If you want to continue to use SAML you can do it in the Enterprise Edition via <i>Setup -> Users -> SAML connections</i>.