[//]: # (werk v2)
# introduce possibility to update discovered service labels
key | value
---------- | ---
date | 2024-02-09T06:58:10+00:00
version | 2.4.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
Prior to this werk, it was not possible to update only the
discovered labels of a service. Updating those were tied
to updating the identified parameters of the service. This
werk introduces the option to update the discovered service
labels only automatically as well as manually. The following
changes were made to introduce this option as well for better
visibility:
* Service discovery page: changed services due to a change in
their labels are now listed under 'Changed services'. Service
labels can be manually updated with dedicated actions targeting
all changed services or a specific service
* Check_MK Discovery service: the service now accounts for
changed services due to label changes. The state of the discovery
service for such cases can also be configured
* Bulk discovery & Periodic service discovery: now have the option
to update labels of changed services
Title: mssql_backup: Correct timezone difference for last backup date
Class: fix
Compatible: compat
Component: checks
Date: 1696949130
Edition: cre
Level: 1
Version: 2.2.0p22
This werk is relevant for users monitoring the age of the last backup time of mssql databases in different timezones.
The date/time of the last backup of a mssql database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone.
When using different timezones, this leads to incorrect values for "Age of last database backup" and if the age is negative, in newer Checkmk versions to the warning "Cannot reasonably calculate time since last backup (hosts time running ahead)".
The mssql agent plugin will now store the time in UTC and the mssql_backup check will interpret the time accordingly.
You will need to update the agent plugin mssql.vbs to receive the corrected times.
Title: Support host & service labels in CSV exports again
Class: fix
Compatible: compat
Component: multisite
Date: 1707413153
Edition: cre
Level: 1
Version: 2.2.0p22
In <a href="https://checkmk.com/werk/13729">Werk #13729</a> support for labels
in CSV exports was removed (among other things). Instead, for affected columns
a constant <code>"NOT_CSV_EXPORTABLE"</code> value was exported.
This change reintroduces host & service labels as JSON serialized strings. This
only relates to CSV exports, other formats are not affected.
Sample export:
C+:
"host";"host_labels"
"test";"{""cmk\/os_platform"": ""linux"", ""cmk\/os_family"": ""linux"", ""cmk\/check_mk_server"": ""yes"", ""cmk\/site"": ""test""}"
"dummy";"{""my_label"": ""works""}"
"nothing";"{}"
C-:
[//]: # (werk v2)
# audit_log: Deprecate 'delete' method and replace it for 'archive'
key | value
---------- | ---
date | 2024-02-09T13:24:13+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
Since the DELETE method actually archives the audit_log entries, this endpoint is
replaced by domain-types/audit_log/actions/archive/invoke
The DELETE endpoint is deprecated and will be removed on version 2.4.0.
In order to update their scripts, users should replace
curl -x DELETE http://host/site/api/1.0/domain-types/audit_log/collections/all
with
curl -x POST http://host/site/api/1.0/domain-types/audit_log/actions/archive/invoke
[//]: # (werk v2)
# Support host & service labels in CSV exports again
key | value
---------- | ---
date | 2024-02-08T17:25:53+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
In [Werk #13729](https://checkmk.com/werk/13729) support for labels in CSV
exports was removed (among other things). Instead, for affected columns a
constant `"NOT_CSV_EXPORTABLE"` value was exported.
This change reintroduces host & service labels as JSON serialized strings. This
only relates to CSV exports, other formats are not affected.
Sample export:
```csv
"host";"host_labels"
"test";"{""cmk\/os_platform"": ""linux"", ""cmk\/os_family"": ""linux"", ""cmk\/check_mk_server"": ""yes"", ""cmk\/site"": ""test""}"
"dummy";"{""my_label"": ""works""}"
"nothing";"{}"
```
[//]: # (werk v2)
# ldap_connection: When you create/clone a new ldap connection, the ID will now be unique
key | value
---------- | ---
date | 2024-02-09T15:54:09+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Previously, when creating a new LDAP connection via the UI, you could provide
an ID that was already in use by another user connection. This is no longer
the case with this werk. Now, when you clone a connection, a new unique ID
will be generated from the cloned connection. If you create a new connection,
the ID must be unique or you will get an error.
Title: mk_inventory: Regression in bakery plugin
Class: fix
Compatible: compat
Component: agents
Date: 1707400951
Edition: cee
Knowledge: doc
Level: 1
Version: 2.2.0p22
This werk fixes a regression that came up with Checkmk 2.2.0,
only affecting windows agents.
While patching the `mk_inventory.vbs` script, the agent bakery
accidentally specified `exe_paths` two times, instead of once
`exePaths` and once `regPaths`.
Title: lnx_video: Fix section parsing
Class: fix
Compatible: compat
Component: checks
Date: 1707412972
Edition: cre
Level: 1
Version: 2.1.0p40
The output of the 'lspci' command was not consistent. This caused the parsing of the lnx_video section to fail.
As a consequnce, the graphics cards were not shown in the HW/SW inventory.
This has now been fixed and the graphics cards will be shown.
Title: Fix inventory sync of subsequent hosts if a previous one has invalid data
Class: fix
Compatible: compat
Component: liveproxy
Date: 1707132754
Edition: cee
Level: 1
Version: 2.2.0p22
Title: Fix inventory sync of hosts if remote data is updated at the time when liveproxyd sync starts or ends
Class: fix
Compatible: compat
Component: liveproxy
Date: 1707132975
Edition: cee
Level: 1
Version: 2.2.0p22
When the liveproxyd starts or ends at a particular time TS and remote inventory
data is written between TS and \<TS+1 then it's not synced.