Checkmk werks level1 July 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
398 discussions

[2.2.0] Checkmk Werk 17002 adapted: Support Azure Databases for MySQL flexible server

by Checkmk werks level 1

Werk 17002 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Support Azure Databases for MySQL flexible server Class: feature Compatible: compat Component: checks Date: 1720519796 Edition: cre Level: 1 Version: 2.2.0p32 Microsoft is retiring the Azure resource "Database for MySQL single server" (see https://learn.microsoft.com/en-us/azure/mysql/migrate/whats-happening-to-my…). With this Werk we now support monitoring the recommended Azure resource "Database for MySQL flexible server". In the rule "Microsoft Azure" under "Azure services to monitor" users can now select the new option "Database for MySQL flexible server". (Note that the former option "Database for MySQL" was renamed to "Database for MySQL single server" and stays in place.) The metrics monitored for flexible servers correspond to those monitored for single servers and the same checks are used. See the <a href="https://checkmk.com/integrations?distributions%5B%5D=check_mk&distribut…">check plugin catalog</a> for more details. ------------------------------------<diff>------------------------------------------- Title: Support Azure Databases for MySQL flexible server Class: feature Compatible: compat Component: checks Date: 1720519796 Edition: cre Level: 1 - Version: 2.2.0p31 ? ^ + Version: 2.2.0p32 ? ^ Microsoft is retiring the Azure resource "Database for MySQL single server" (see https://learn.microsoft.com/en-us/azure/mysql/migrate/whats-happening-to-my…). With this Werk we now support monitoring the recommended Azure resource "Database for MySQL flexible server". In the rule "Microsoft Azure" under "Azure services to monitor" users can now select the new option "Database for MySQL flexible server". (Note that the former option "Database for MySQL" was renamed to "Database for MySQL single server" and stays in place.) The metrics monitored for flexible servers correspond to those monitored for single servers and the same checks are used. See the <a href="https://checkmk.com/integrations?distributions%5B%5D=check_mk&distribut…">check plugin catalog</a> for more details.

2 months

[2.2.0] Checkmk Werk 16990 created: NagVis: Updated to 1.9.42 (fix security issues)

by Checkmk werks level 1

Title: NagVis: Updated to 1.9.42 (fix security issues) Class: security Compatible: compat Component: packages Date: 1720609589 Edition: cre Level: 1 Version: 2.2.0p31 NagVis has been updated to version 1.9.42. This update fixes the following security issues: - Fix various XSS issues (CVSS score: 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) - Fix potential RCE - Fix insecure password hashing algorithm for dedicated NagVis users (CVSS score 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) - Fix leak of installation path in error messages - Fix Make cookie hash comparison timing safe

2 months

[2.3.0] Checkmk Werk 16117 created: Fix path for snmpget in check_snmp and check_hpjd

by Checkmk werks level 1

[//]: # (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.

2 months

[2.3.0] Checkmk Werk 17092 adapted: Fix missing CSRF token issues

by Checkmk werks level 1

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.

2 months

[2.3.0] Checkmk Werk 17174 created: REST API: removal of previously deprecated endpoints

by Checkmk werks level 1

[//]: # (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`

2 months

[2.3.0] Checkmk Werk 17115 created: HPE Proliant Servers: RAID Controllers: Adapt to changes in iLO firmware

by Checkmk werks level 1

[//]: # (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.

2 months

[2.3.0] Checkmk Werk 16991 created: Extraneous characters in rule representation

by Checkmk werks level 1

[//]: # (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.

2 months

[2.3.0] Checkmk Werk 17073 created: Siemens PLC agent configuration: Take timeout parameter into account

by Checkmk werks level 1

[//]: # (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.

2 months

[2.3.0] Checkmk Werk 16990 created: NagVis: Updated to 1.9.42 (fix security issues)

by Checkmk werks level 1

[//]: # (werk v2) # NagVis: Updated to 1.9.42 (fix security issues) key | value ---------- | --- date | 2024-07-10T11:06:29+00:00 version | 2.3.0p10 class | security edition | cre component | packages level | 1 compatible | yes NagVis has been updated to version 1.9.42. This update fixes the following security issues: - Fix various XSS issues (CVSS score: 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) - Fix potential RCE - Fix insecure password hashing algorithm for dedicated NagVis users (CVSS score 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) - Fix leak of installation path in error messages - Fix Make cookie hash comparison timing safe

2 months

[2.3.0] Checkmk Werk 17155 adapted: Microsoft Teams: Use workflows instead of connectors

by Checkmk werks level 1

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.

2 months

← Newer
1
...
12
13
14
15
16
17
18
...
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2024