Werk 16675 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Remove unused evaluation type specification
key | value
---------- | ---
date | 2024-04-04T10:58:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other.
However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type.
For the affected rule specs this option was removed:
* AgentConfig
* NotificationParameters
* DiscoveryParameters
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Remove unused evaluation type specification
key | value
---------- | ---
date | 2024-04-04T10:58:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other.
However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type.
For the affected rule specs this option was removed:
* AgentConfig
* NotificationParameters
+ * DiscoveryParameters
Werk 16675 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Ruleset API: Remove unused evaluation type specification
key | value
---------- | ---
date | 2024-04-04T10:58:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other.
However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type.
For the affected rule specs this option was removed:
* AgentConfig
* NotificationParameters
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Ruleset API: Remove unused evaluation type specification
key | value
---------- | ---
date | 2024-04-04T10:58:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other.
However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type.
For the affected rule specs this option was removed:
* AgentConfig
+ * NotificationParameters
[//]: # (werk v2)
# Ruleset API: Remove unused evaluation type specification
key | value
---------- | ---
date | 2024-04-04T10:58:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | no
This change is only relevant for plugin developers.
Some rule specs allow the configuration of the `eval_type` to specify how the rules are meant to be evaluated in respect to each other.
However, this configuration is not considered in some cases, instead Checkmk uses a predetermined evaluation type.
For the affected rule specs this option was removed:
* AgentConfig
[//]: # (werk v2)
# Dashboard: Fix event statistics not displaying information if no events found
key | value
---------- | ---
date | 2024-03-20T10:34:20+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Prior to this Werk, if no events were found, the event statistics
dashlet was drawn empty. This Werk corrects that behaviour and if
no events are found, the graph should show with a count of zero.
[//]: # (werk v2)
# check_cert: New active check for advanced certificate monitoring
key | value
---------- | ---
date | 2024-04-03T13:42:35+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | yes
The _check_http_ plug-in was previously the only method to monitor
certificates out-of-the-box with Checkmk. With the new plug-in Checkmk
provides an extensive functionality to monitor certificates. This includes
but is not limited to certificates provided by the HTTP protocol.
With the new plug-in you can monitor all certificates provided through
a TCP connection to encrypt communication. This includes the monitoring
of
* validity times (max and remaining)
* issuer fields
* subject fields
* encryption algorithm
* alternative names
* response times
* public key algorithm and size
* serial number
As with the reworked plugin to monitor web services, you are able to
configure multiple services within a single rule.
[//]: # (werk v2)
# check_http: Soft deprecatation of old HTTP monitoring plug-in
key | value
---------- | ---
date | 2024-04-03T13:15:48+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | no
The old plug-in is being deprecated in a soft way with this werk. Unlike
hard deprecation, the deprecated rule set "Check HTTP service" will remain
fully functional. However, new rules should only be created if absolutely
necessary, such as when experiencing issues with the new "Check HTTP web
service" implementation and needing to roll back to the old one.
Please note that the rule set will be hard deprecated in version 2.4.0,
meaning that you will no longer be able to create new rules. However, the
plug-in itself will remain available as this is a component of the
monitoring-plugins collection that comes with Checkmk.
Please know us know if you find any features that were present in the old
plug-in but are missing in the new one.
[//]: # (werk v2)
# notifications: Fix plugin permissions not loaded automatically
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-03-27T14:22:37+00:00
level | 1
class | fix
component | notifications
edition | cre
Previously, it was possible for users with the "Notification configuration"
permission to edit notification rules even if they did not have the permission
to the plugin that was being used in the rule. When such a user edited
such a rule, they were able to overwrite the notification plugin with
any plugin they were allowed to use.
This werk stops users from editing rules that use notification plugins
they don't have access to.
[//]: # (werk v2)
# Enforcing password change redirect with 2FA enabled
key | value
---------- | ---
date | 2024-04-04T14:47:34+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Before this werk, the site failed to redirect users to the
"Change Password" page following a successful login when
two-factor authentication (2FA) was enabled. This werk resolves
the issue by ensuring that, after completing 2FA, users are now
redirected correctly.
[//]: # (werk v2)
# Split BI availability timeline livestatus query
key | value
---------- | ---
date | 2024-02-12T09:14:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
When retrieving BI availability timeline data for a time range greater than one
month the livestatus query is split into multiple queries.
The reason for this is to avoid reaching the maximum limit for the size of the
livestatus response.