[//]: # (werk v2)
# Jira: Add API/PAT token authentication option
key | value
---------- | ---
date | 2024-07-16T08:56:18+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | no
You can now use an API (Jira Cloud) or Personal access token (Jira on premise)
to authenticate. This is availabe in the new "Authentication" section of the
notification rule for Jira. Please see the inline help for more informations.
As basic auth is deprecated for Jira Cloud, please update your notification
rule configuration.
[//]: # (werk v2)
# Jira: Add option to set assignee
key | value
---------- | ---
date | 2024-07-11T14:20:48+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
You can now use the new option "Assignee" to assign created issues to a
defined user. Please use the username (not the Email) of the Jira user.
If this option is unchecked, the issue will be created unassigned.
[//]: # (werk v2)
# Jira: Clarify authentification option
key | value
---------- | ---
date | 2024-07-11T11:47:04+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | no
The former "Password" option was renamed to "API/Access". Furthermore, the
inline help was adjusted to clarify what has to be used in which case.
[//]: # (werk v2)
# Jira: Allow macros in label
key | value
---------- | ---
date | 2024-07-11T10:11:38+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
You can now use all macros that are defined in the notification context in the
"Label" option of the JIRA notification plugin.
[//]: # (werk v2)
# Integrate popular "Ceph statistics" plugin
key | value
---------- | ---
date | 2024-07-08T11:22:28+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
This werk integrates the popular Ceph plugin written by Robert Sander into Checkmk.
This adds the plugins
* Ceph Storage: Status
* Ceph Storage: Pools
* Ceph Storage: Classes
* Ceph Storage: OSD - BlueFS Slow Device
* Ceph Storage: OSD - BlueFS Database Device
* Ceph Storage: OSD - BlueFS Write-Ahead Log
Enterprise users can deploy the agent plugin using the bakery ruleset _"Ceph (Linux)"_.
It requires python and the third party python library 'rados' to be installed.
Users who previously used Robert Sanders MKP [Ceph statistics](https://exchange.checkmk.com/p/ceph) should upgrade it to the most recent version, which shall disable itself upon upgrade to Checkmk 2.4.
(This werk will be updated once the version is confirmed.)
The only change will be the renamed host labels, that all get the _"cmk/"_ prefix (_"ceph/osd"_ becomes "_cmk/ceph/osd"_ and _"ceph/mon"_ becomes _"cmk/ceph/mon"_).
Since it provides a more comprehensive monitoring of Ceph devices, it will replace the previous Ceph plugins
* Ceph Storage: Health Status
* Ceph Storage: OSDs
* Ceph Storage: PGs
* Ceph Storage: MGRs
* Ceph Storage: Pools
These plugins will continue to work in Checkmk 2.4 as long as an agent is deployed using the old agent plugin.
New deployments however will contain the new plugin.
[//]: # (werk v2)
# Monitor CPU, Memory, Tasks and Active time reported from systemd
key | value
---------- | ---
date | 2024-07-12T07:44:08+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
The monitoring of systemd's single services is now extended to report CPU Time, memory, number of tasks and the time the service is active.
The information was already reported by the agent and is now also evaluated in the check plugin.
[//]: # (werk v2)
# Fix path for snmpget in check_snmp and check_hpjd
key | value
---------- | ---
date | 2024-07-16T08:39:01+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Werk 13585 introduced a bug in the path calculation for snmpget, so the
check_snmp and check_hpjd active checks failed randomly. This has been
fixed.
[//]: # (werk v2)
# HPE Proliant Servers: RAID Controllers: Adapt to changes in iLO firmware
key | value
---------- | ---
date | 2024-07-10T12:16:12+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes crashes in the plugin "HPE Proliant Servers: RAID Controllers".
A recent update of the HPE iLO firmware left Checkmk unable to interpret some of the reported states.
Werk 17146 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# Remove etc/apache/conf.d/var_www.conf
key | value
---------- | ---
date | 2024-07-15T12:21:48+00:00
version | 2.4.0b1
class | feature
edition | cre
component | multisite
level | 1
compatible | no
Checkmk used to come with an apache config file `etc/apache/conf.d/var_www.conf`.
By default this file added/enabled directory listing for sub-directories under `var/www/`.
The main folder `var/www` was not listed though since the URL is redirected to Checkmk.
In order to simplify the configuration we drop that file.
If you edited that file you will be asked if you want to keep it upon update.
If you relied on the directory listing you can enable it again e.g. by copying the file from an older version.
[//]: # (werk v2)
# Rest API: change response codes for some endpoints from 302 to 303
key | value
---------- | ---
date | 2024-07-11T14:48:17+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
Some endpoints accept some data (via POST, PUT), start a background job and then
redirect to other "wait-for-completion" endpoints. The wait-for-completion
endpoints however expected requests with the GET method.
Previously, we used the response code "302 Found" in these cases. Some clients,
like the python requests library, always change the method to GET on redirects,
but this is not according to the spec. As such "correct" clients ran into issues
so we made the decision to update these endpoints to use "303 See other"
instead. This status code guarantees a change to the GET method.
Affected endpoints:
* Execute service discovery on host
(`/domain-types/service_discovery_run/actions/start/invoke`)
* Rename a host
(`/objects/host_config/example.com/actions/rename/invoke`)
* Activate pending changes
(`/domain-types/activation_run/actions/activate-changes/invoke`)