[//]: # (werk v2)
# ewon: KeyError (device)
key | value
---------- | ---
date | 2024-08-06T07:48:07+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
An existing rule for `check_ewon` without the mandatory key `device` would result in an exception
`KeyError (device)`.
This change makes the check function use a default, if `device` is not set.
[//]: # (werk v2)
# check_ewon: ValueError (incomplete format)
key | value
---------- | ---
date | 2024-08-06T07:52:50+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Formatting a value with unit `%` would result in an invalid format-string making `check_ewon`
crash with an exception `ValueError (incomplete format)`.
This change makes `check_ewon` use f-formatting instead of `%`-formatting.
Werk 16026 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Add support for SLES 15 SP6
key | value
---------- | ---
date | 2024-08-14T07:25:20+00:00
version | 2.4.0b1
class | feature
edition | cre
component | omd
level | 1
compatible | yes
With this werk, Checkmk is build for SLES 15 SP6
[//]: # (werk v2)
# Introduce global setting: Default dynamic visuals permission
key | value
---------- | ---
date | 2024-07-24T10:15:09+00:00
version | 2.4.0b1
class | feature
edition | cre
component | multisite
level | 1
compatible | yes
Introduce a new global setting, called 'Default dynamic visuals permission',
which can be used to change the default permission for all roles
(including built-in roles) of dynamic visuals such as custom dashboards, views,
etc.
If set to 'yes' all roles will have the permission to access these visuals by
default. If set to 'no' only the admin role will be able to access the dynamic
visuals.
[//]: # (werk v2)
# Add support for SLES 15 SP6
key | value
---------- | ---
date | 2024-08-14T07:25:20+00:00
version | 2.4.0b1
class | feature
edition | cre
component | omd
level | 1
compatible | yes
With this werk, Checkmk is build for SLES 15 SP6
[//]: # (werk v2)
# notification rules: align the REST-API with the UI for the Servicenow plugin
key | value
---------- | ---
date | 2024-08-16T14:02:00+00:00
version | 2.4.0b1
class | fix
edition | cre
component | notifications
level | 1
compatible | no
The Servicenow plugin method for notification rules recently has some improvements.
You can now select between Basic authentication or Token authentication. For
each of these you can also select a password store id. This werk aligns the
REST-API with this improved configuration.
[//]: # (werk v2)
# notification rules: align the REST-API with the UI for the Jira plugin config
key | value
---------- | ---
date | 2024-08-16T05:32:46+00:00
version | 2.4.0b1
class | fix
edition | cee
component | rest-api
level | 1
compatible | no
The Jira plugin method for notification rules recently had some improvments.
You can now select between Basic authentication or a Personal access token.
For each of these you can also select a password store id. This werk aligns
the REST-API with this improved configuration.
[//]: # (werk v2)
# Fix warning on rule creation of "Icon image for..."
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-08-15T12:53:28+00:00
level | 1
class | fix
component | wato
edition | cre
If you created a new rule "Icon image for hosts in status GUI" or "Icon image
for services in status GUI", a warning like "Unable to read current options of
this rule" was shown.
The rule could still be created.
[//]: # (werk v2)
# Opsgenie_issues: add ability to config extra properties in notification
key | value
---------- | ---
date | 2024-08-16T08:46:06+00:00
version | 2.4.0b1
class | feature
edition | cre
component | notifications
level | 1
compatible | yes
When configuring a notification rule using the Opsgenie_issues plugin,
you can now configure "extra_properties". This new configurable
option is available in both the UI and the REST-API. Extra properties
that you can configure, include
* Site ID
* Tags of the host
* IP address of the host
* Absolute time of the alert
* Relative time of the alert
* Additional plug-in output
* Acknowledgement author
* Acknowledgement comment
* Metrics
* Custom host/service notes URL
* Complete variable list
We now also allow for macros with the Tags in the Opsgenie_issues plugin.
[//]: # (werk v2)
# Custom graphs: Re-work unit configuration
key | value
---------- | ---
date | 2024-08-09T12:19:52+00:00
version | 2.4.0b1
class | feature
edition | cee
component | multisite
level | 1
compatible | yes
Before this werk, the unit of a custom graph was configured by selecting from a pre-defined list of
units. As of this werk, users have two configuration options:
* **First entry with unit**
With this setting, the unit of the graph will be set to the unit of the first entry of the custom
graph that as a known unit. Metrics and scalars always have a known unit. Constants on the other
hand do not. For operations, it depends on the type of operation. For example, the unit of a sum
of metrics is computed by traversing through the elements of the sum and using the first found
unit. On the other hand, the unit of a product is unknown. If no entry has a known unit, the graph
will be rendered without a unit symbol.
* **Custom**
This setting opens a sub-dialogue that allows users to customize the graph unit. Users can select
from multiple notations, set the unit symbol the and the number of decimal places.
When updating to Checkmk 2.4, in most cases, existing custom graphs will be updated automatically to
retain the currently configured unit. The rare cases where this is not possible will be set to
"First entry with unit" during the update.