Title: omd start mkeventd: Error Code of Event Daemon
Class: fix
Compatible: compat
Component: omd
Date: 1706877168
Edition: cre
Level: 1
Version: 2.2.0p22
The command <code>omd start mkeventd</code> 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 <code>Failed</code> is
shown and the command <code>omd start mkeventd</code> exits with error code 2.
[//]: # (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.4.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)
# Hide private topics in dropdowns
key | value
---------- | ---
date | 2024-02-01T08:07:44+00:00
version | 2.4.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 pagetypes being falsely shown as public
key | value
---------- | ---
date | 2024-02-01T08:01:39+00:00
version | 2.4.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)
# omd start mkeventd: Error Code of Event Daemon
key | value
---------- | ---
date | 2024-02-02T12:32:48+00:00
version | 2.4.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)
# Import Azure tags as service labels
key | value
---------- | ---
date | 2024-01-29T07:26:41+00:00
version | 2.4.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.4.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.
Title: Fix for 'ERROR: Failed to read config of site' of existing site when creating a new one
Class: fix
Compatible: compat
Component: omd
Date: 1706696943
Edition: cre
Level: 1
Version: 2.1.0p39
When creating a new site while having other sites the new site tries to determine the used ports of the other sites with checking their 'etc/omd/site.conf'.
If this file is not accessible an error 'ERROR: Failed to read config of site ...' is shown.
This happens e.g. if a root user with a restictive umask (e.g. 0077) creates a site.
The site folder has then only owner and group permissions set while "other" does not have any permissions. After this site folder and the site user is created omd switches to that user and creates the file and folder structure with defined permissions. So that 'etc/omd/site.conf' is other-readable.
Since the site folder is missing the executable permission for other this folder is not traversable therefore the files and folders beneath are inaccessible.
With this change we make sure that the site folder has at least the executable permission for other.
For already existing sites this change has no affect. If the error 'ERROR: Failed to read config of site ...' is still shown make sure that existing site folders have that other executable permission,
e.g. by 'chmod o+x /omd/sites/\<SITENAME\>'.
Title: service discovery: introduce functionality to fetch job status from remote sites
Class: fix
Compatible: compat
Component: rest-api
Date: 1706523804
Edition: cre
Level: 1
Version: 2.2.0p22
Prior to this werk, the service discovery endpoints were restricted to the local
service discovery background job. This resulted in the following endpoints being
restricted to local setups only:
LI: Show the last service discovery background job on a host
LI: Wait for service discovery completion
This werk fixes this and now also supports distributed monitoring setups. To benefit
from this change both the central site as well the remote sites need to be updated
to the werk's version. This change does not affect local only setups.
[//]: # (werk v2)
# netapp_ontap_environment: show unit of measurement in summary
key | value
---------- | ---
compatible | yes
version | 2.4.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.