Checkmk werks level1 July 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
398 discussions

[2.4.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.4.0b1 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.4.0b1 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

[2.4.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.4.0b1 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.4.0b1 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

[2.4.0] Checkmk Werk 17155 created: Microsoft Teams: Use workflows instead of connectors

by Checkmk werks level 1

[//]: # (werk v2) # Microsoft Teams: Use workflows instead of connectors key | value ---------- | --- date | 2024-07-15T08:57:21+00:00 version | 2.4.0b1 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.

2 months

[2.4.0] Checkmk Werk 17126 created: azure_mysql_connections, azure_postgresql_connections: Add lower levels for active connections

by Checkmk werks level 1

[//]: # (werk v2) # azure_mysql_connections, azure_postgresql_connections: Add lower levels for active connections key | value ---------- | --- date | 2024-07-12T09:24:48+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes

2 months

[2.4.0] Checkmk Werk 17002 created: Support Azure Databases for MySQL flexible server

by Checkmk werks level 1

[//]: # (werk v2) # Support Azure Databases for MySQL flexible server key | value ---------- | --- date | 2024-07-09T10:09:56+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes 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 [check plugin catalog](https://checkmk.com/integrations?distributions%5B%5D=check_mk&dist… for more details.

2 months

[2.3.0] Checkmk Werk 16440 created: kube: ValueError: not enough values to unpack

by Checkmk werks level 1

[//]: # (werk v2) # kube: ValueError: not enough values to unpack key | value ---------- | --- date | 2024-07-12T12:02:32+00:00 version | 2.3.0p10 class | fix edition | cre component | checks level | 1 compatible | yes This error affects users, which use the `Kubernetes` special agent, and have enabled the option `Persistent Volume Claims`. It is a regression, which was introduced in Checkmk version 2.3.0. Previously, the agent could crash with the following error. ``` File "/omd/sites/cmksite/lib/python3/cmk/special_agents/utils_kubernetes/transform_any.py", line 39, in _parse_metric_sample_with_labels value_string, *_optional_timestamp = timestamped_value.strip().split() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ValueError: not enough values to unpack (expected at least 1, got 0) ``` This error occured sporadically, if the agent was unable to contact the `kubelet` via the Kubernets API. The error is now reported via the `Kubelet` Service. This is the same behaviour as in Checkmk 2.2.0.

2 months, 1 week

[2.4.0] Checkmk Werk 17079 created: mk_redis: Autodetect Checkmk instances

by Checkmk werks level 1

[//]: # (werk v2) # mk_redis: Autodetect Checkmk instances key | value ---------- | --- date | 2024-06-18T07:27:41+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes Previously the redis agent plugin configured to autodetect would not detect the Checkmk redis instances. Now, on hosts running a Checkmk site, these instances can be autodetected as well and monitored as any other redis instance.

2 months, 1 week

[2.4.0] Checkmk Werk 16440 created: kube: ValueError: not enough values to unpack

by Checkmk werks level 1

[//]: # (werk v2) # kube: ValueError: not enough values to unpack key | value ---------- | --- date | 2024-07-12T12:02:32+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes This error affects users, which use the `Kubernetes` special agent, and have enabled the option `Persistent Volume Claims`. It is a regression, which was introduced in Checkmk version 2.3.0. Previously, the agent could crash with the following error. ``` File "/omd/sites/cmksite/lib/python3/cmk/special_agents/utils_kubernetes/transform_any.py", line 39, in _parse_metric_sample_with_labels value_string, *_optional_timestamp = timestamped_value.strip().split() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ValueError: not enough values to unpack (expected at least 1, got 0) ``` This error occured sporadically, if the agent was unable to contact the `kubelet` via the Kubernets API. The error is now reported via the `Kubelet` Service. This is the same behaviour as in Checkmk 2.2.0.

2 months, 1 week

[2.2.0] Checkmk Werk 16562 adapted: Fix automatic host registration and removal in case one remote site is not logged in

by Checkmk werks level 1

Werk 16562 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Fix automatic host registration and removal in case one remote site is not logged in Class: fix Compatible: compat Component: wato Date: 1720418941 Edition: cre Level: 1 Version: 2.2.0p31 The automatic host registration and removal jobs are executed regularly in the background to add or remove hosts. These are fundamental mechanisms to the automatic host registration. The jobs failed completely in case one remote site was configured but not logged in, not only affecting the not logged in site, but all sites. The not logged in site is now being skipped, leaving the mechanism intact for all other sites. ------------------------------------<diff>------------------------------------------- - Title: Fix automatic host removal in case one remote site is not logged in + Title: Fix automatic host registration and removal in case one remote site is not logged in ? +++++++++++++++++ Class: fix Compatible: compat Component: wato Date: 1720418941 Edition: cre Level: 1 Version: 2.2.0p31 - The automatic host removal job is executed regularly in the background to remove - hosts from the monitoring once they cease to exist. In particular for but not - limited to automatically registered hosts. + The automatic host registration and removal jobs are executed regularly in the + background to add or remove hosts. These are fundamental mechanisms to the + automatic host registration. - This job failed in case one remote site was configured but not logged in, not ? ^^ -------- + The jobs failed completely in case one remote site was configured but not logged ? ^ + +++++++++++ - only affecting the not logged in site, but all sites. The not logged in site is ? -------- + in, not only affecting the not logged in site, but all sites. The not logged in ? ++++++++ - now being skipped, leaving the mechanism intact for all other sites. + site is now being skipped, leaving the mechanism intact for all other sites. ? ++++++++

2 months, 1 week

[2.3.0] Checkmk Werk 17125 created: Perfometer: Fix 'Exception: VALUE' if a value exceeds the upper, closed boundary

by Checkmk werks level 1

[//]: # (werk v2) # Perfometer: Fix 'Exception: VALUE' if a value exceeds the upper, closed boundary key | value ---------- | --- date | 2024-07-11T10:24:38+00:00 version | 2.3.0p10 class | fix edition | cre component | multisite level | 1 compatible | yes

2 months, 1 week

← Newer
1
...
21
22
23
24
25
26
27
...
40
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2024