[//]: # (werk v2)
# Microsoft Teams: Use workflows instead of connectors
key | value
---------- | ---
date | 2024-07-15T08:57:21+00:00
version | 2.3.0p11
class | fix
edition | cre
component | notifications
level | 1
compatible | no
Since Microsoft announced the deprecation of connectors, the notification
plugin for Microsoft Teams was adjusted to use workflows.
Deprecation note:
https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-con…
To configure a workflow within Microsoft Teams:
* Click the 3 dots on a channel and select “Workflows”
* Choose "Post to a channel when a webhook request is received"
* Choose name for the workflow, e.g. "Checkmk"
* Select team and channel where the webhook should post to
* Copy webhook URL
For further informations please see section "How do I transition from Office
365 connectors to Workflows?" in the deprecation note.
To configure the notification plugin within Checkmk:
* Post copied webhook URL to "Webhook URL" of your notification rule for MS Teams
If you used custom "Details for host notifications" or "Details for service
notifications", the line break "<br\>" has to be replaced by "\\u00A0\\n".
As we now use Adaptive Cards instead of Message Cards, we can no longer use
colors.
[//]: # (werk v2)
# Jira: Add update of issues on state changes
key | value
---------- | ---
date | 2024-07-16T11:20:44+00:00
version | 2.4.0b1
class | feature
edition | cee
component | notifications
level | 1
compatible | yes
Before this werk, state changes like "WARN" to "CRIT" did not update existing
issues.
This is now the default behaviour if state changes to none "OK" states happen.
[//]: # (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.