[//]: # (werk v2)
# Respect timerange for all view elements in report
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-09T10:20:05+00:00
level | 1
class | fix
component | reporting
edition | cee
If a report with more than one view element was created e.g. via the report
snapin, the defined timerange was only set from the second view element on.
[//]: # (werk v2)
# "Aggregation of Downtimes" BI option had no effect
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-15T07:48:10+00:00
level | 1
class | fix
component | bi
edition | cre
The option should change the computation of downtimes from CRIT to WARN but did
not. This has been fixed.
Werk 15584 was deleted. The following Werk is no longer relevant.
Title: mk_docker: Added podman support
Class: feature
Compatible: compat
Component: checks
Date: 1683627763
Edition: cre
Knowledge: undoc
Level: 1
Version: 2.3.0b1
Added podman support in mk_docker.py.
This way the plugin ends in case it is being executed on a non docker or podman host.
[//]: # (werk v2)
# nfsiostat: resolve error when displaying graphs
key | value
---------- | ---
date | 2024-02-12T10:44:11+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
There was an error in the nfsiostat plugin where it tried
to report some data in units not supported by the graphing
system which made viewing its service graphs impossible.
This werk changes the units that were reported to our
visualizations and now the graphs render all data appropriately.
[//]: # (werk v2)
# EC: Fix missing update action for CRE
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-02-15T08:47:52+00:00
level | 1
class | fix
component | ec
edition | cre
With werk 16012 the active configuration folder was introduced. During an
update the event console configuration is synchronized to this folder which is
missing for the raw edition. Fixed that.
Werk 16337 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# mk_inventory: Fix for lnx_video when multiple graphics cards are available
key | value
---------- | ---
date | 2024-02-12T12:30:17+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
When multiple graphics cards were present, the command 'lscpi -s: Invalid bus number'.
This left the section blank and no cards were detected in the HW/SW inventory.
This fix may cause new graphics cards to appear in the HW/SW inventory.
For the fix to take effect, the user will need to re-deploy the plugin.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# mk_inventory: Fix for lnx_video when multiple graphics cards are available
key | value
---------- | ---
date | 2024-02-12T12:30:17+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
When multiple graphics cards were present, the command 'lscpi -s: Invalid bus number'.
- This left the section blank and no services were detected.
? -------
+ This left the section blank and no cards were detected in the HW/SW inventory.
? ++++ +++++++++++++++++++++++
- This fix may cause new services to appear.
+ This fix may cause new graphics cards to appear in the HW/SW inventory.
For the fix to take effect, the user will need to re-deploy the plugin.
- It may also be necessary to run the service discovery manually.
[//]: # (werk v2)
# mk_inventory: Fix for lnx_video when multiple graphics cards are available
key | value
---------- | ---
date | 2024-02-12T12:30:17+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
When multiple graphics cards were present, the command 'lscpi -s: Invalid bus number'.
This left the section blank and no services were detected.
This fix may cause new services to appear.
For the fix to take effect, the user will need to re-deploy the plugin.
It may also be necessary to run the service discovery manually.
[//]: # (werk v2)
# introduce possibility to update discovered service labels
key | value
---------- | ---
date | 2024-02-09T06:58:10+00:00
version | 2.3.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
[//]: # (werk v2)
# audit_log: Deprecate 'delete' method and replace it for 'archive'
key | value
---------- | ---
date | 2024-02-09T13:24:13+00:00
version | 2.3.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.3.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";"{}"
```