[//]: # (werk v2)
# Fix path for snmpget in check_snmp and check_hpjd
key | value
---------- | ---
date | 2024-07-16T08:39:01+00:00
version | 2.3.0p11
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 17092 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fix missing CSRF token issues
key | value
---------- | ---
date | 2024-07-03T09:07:10+00:00
version | 2.3.0p9
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Werk #17090 in Checkmk 2.3.0p8 and 2.2.0p29 introduced additional CSRF token checks in the GUI.
This caused some buttons to not work anymore because the CSRF token was missing, including, but likely not limited to:
* "Synchronize users" in Setup > Users to manually trigger the LDAP sync (the background sync still runs)
* "Show analysis" and "Show bulks" in Setup > Events > Notifications
* Reordering notification rules via drag-and-drop in the same view
* "Bake agents" in the agent bakery (as a workaround, use "Bake and sign agents")
* "Acknowledge last baking result" when a bake job failed (as a workaround, delete the failed job instead)
This Werk fixes the issues by adding the token.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Fix missing CSRF token issues
key | value
---------- | ---
date | 2024-07-03T09:07:10+00:00
- version | 2.3.0p11
? ^^
+ version | 2.3.0p9
? ^
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Werk #17090 in Checkmk 2.3.0p8 and 2.2.0p29 introduced additional CSRF token checks in the GUI.
This caused some buttons to not work anymore because the CSRF token was missing, including, but likely not limited to:
* "Synchronize users" in Setup > Users to manually trigger the LDAP sync (the background sync still runs)
* "Show analysis" and "Show bulks" in Setup > Events > Notifications
* Reordering notification rules via drag-and-drop in the same view
* "Bake agents" in the agent bakery (as a workaround, use "Bake and sign agents")
* "Acknowledge last baking result" when a bake job failed (as a workaround, delete the failed job instead)
This Werk fixes the issues by adding the token.
[//]: # (werk v2)
# REST API: removal of previously deprecated endpoints
key | value
---------- | ---
date | 2024-07-15T13:58:34+00:00
version | 2.3.0p11
class | fix
edition | cre
component | rest-api
level | 1
compatible | no
With this werk previously deprecated endpoints will be removed.
The following endpoints are affected, see their respective werks for details:
* [Werk 14537](https://checkmk.com/werk/14537): `/domain-types/service/collections/services`
* [Werk 14538](https://checkmk.com/werk/14538): `/objects/host/{host_name}/actions/discover_services/invoke`
* [Werk 16367](https://checkmk.com/werk/16367): `/domain-types/audit_log/collections/all`
[//]: # (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.3.0p11
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 v2)
# Extraneous characters in rule representation
key | value
---------- | ---
date | 2024-07-15T07:23:03+00:00
version | 2.3.0p11
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
With long rulesets, the rule representation (Export this rule for API) often
would display extraneous characters such as newlines or whitespace.
This did not affect the functionality of the feature, but could be confusing, so now
these characters are no longer displayed.
[//]: # (werk v2)
# Siemens PLC agent configuration: Take timeout parameter into account
key | value
---------- | ---
date | 2024-07-12T10:47:29+00:00
version | 2.3.0p11
class | fix
edition | cre
component | checks
level | 1
compatible | yes
When configuring the Siemens PLC agent, users could configure a per-device timeout. However, the
configured values had no effect. Instead, the agent always used a default value of 10 seconds. As
of this werk, users can instead configure one global timeout value, which is taken into account by
the agent.
Werk 17155 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (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.
------------------------------------<diff>-------------------------------------------
[//]: # (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".
? ^ ^^
+ 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)
# 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.