Checkmk werks level1 May 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
549 discussions

[2.3.0] Checkmk Werk 16528 adapted: reports: remove site_id of other customers when rendering reports

by Checkmk werks level 1

Werk 16528 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # reports: remove site_id of other customers when rendering reports key | value ---------- | --- date | 2024-04-18T07:21:06+00:00 version | 2.3.0p1 class | fix edition | cme component | reporting level | 1 compatible | yes When you try to create a report and a remote site is not reachable, the report will include the site_id of said site. This werk addresses this issue by only showing errors that belong to that customer. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # reports: remove site_id of other customers when rendering reports key | value ---------- | --- date | 2024-04-18T07:21:06+00:00 - version | 2.3.0b7 ? ^^ + version | 2.3.0p1 ? ^^ class | fix edition | cme component | reporting level | 1 compatible | yes When you try to create a report and a remote site is not reachable, the report will include the site_id of said site. This werk addresses this issue by only showing errors that belong to that customer.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16274 adapted: Unusable services for "HPE Proliant Servers: Raid Status"

by Checkmk werks level 1

Werk 16274 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Unusable services for "HPE Proliant Servers: Raid Status" key | value --- | --- compatible | no version | 2.3.0b1 date | 2023-12-15T10:35:33+00:00 level | 1 class | fix component | checks edition | cre This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitoring history by running ``` sed -i 's|\\x00|\\\\x00|' var/check_mk/core/history var/check_mk/core/archive/* ``` ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Unusable services for "HPE Proliant Servers: Raid Status" key | value --- | --- compatible | no version | 2.3.0b1 date | 2023-12-15T10:35:33+00:00 level | 1 class | fix component | checks edition | cre This fixes some unusable services of the "HPE Proliant Servers: Raid Status" plugin. This werk only affects you if you observe unknown "Logical device <ITEM>" services after the upgrade. In case you are affected please run a discovery on the affected hosts and fix the monitoring history as described below. We observed some devices to send `"\x00"` (the null-byte) as their name (`OID .1.3.6.1.4.1.232.3.2.3.1.1.14`). Not all components delt well with it, leading to unacknowlegable downtimes, non matching rules and the like. We now replace all null-bytes with `"\\x00"` (the literal containing the four characters backslash, 'x', 'zero', 'zero'). As of Checkmk 2.3, this should in fact no longer be necessary, but as we need a backportable solution, we change the item consistently in all versions. If this affects you, you might also want to fix the services in the monitoring history by running ``` - sed -i 's|\x00|\\x00|' var/check_mk/core/history var/check_mk/core/archive/* + sed -i 's|\\x00|\\\\x00|' var/check_mk/core/history var/check_mk/core/archive/* ? + ++ ```

3 months, 3 weeks

[2.3.0] Checkmk Werk 16810 created: Fixed sed command in Werk #16274

by Checkmk werks level 1

[//]: # (werk v2) # Fixed sed command in Werk #16274 key | value ---------- | --- date | 2024-04-25T12:03:09+00:00 version | 2.3.0p1 class | fix edition | cre component | checks level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16425 created: APACHE_TCP_ADDR now allows IPv6 address

by Checkmk werks level 1

[//]: # (werk v2) # APACHE_TCP_ADDR now allows IPv6 address key | value ---------- | --- date | 2024-04-22T11:05:16+00:00 version | 2.3.0p1 class | fix edition | cre component | omd level | 1 compatible | yes Previously, using the command `omd config set APACHE_TCP_ADDR` with a IPv6 address would fail. For example, the command ``` $ omd config set APACHE_TCP_ADDR "[::]" ``` resulted in `Invalid value for '[::]'. Does not match allowed pattern.` With this Werk, it `omd` only checks that a `Listen` directive for Apache can be constructed from the `APACHE_TCP_ADDR`. In particular, this a IPv6 address can be configured. Such an address must be surrounded by square brackets.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16528 created: reports: remove site_id of other customers when rendering reports

by Checkmk werks level 1

[//]: # (werk v2) # reports: remove site_id of other customers when rendering reports key | value ---------- | --- date | 2024-04-18T07:21:06+00:00 version | 2.3.0b7 class | fix edition | cme component | reporting level | 1 compatible | yes When you try to create a report and a remote site is not reachable, the report will include the site_id of said site. This werk addresses this issue by only showing errors that belong to that customer.

3 months, 3 weeks

[2.3.0] Checkmk Werk 14231 created: Aggregation visualization: Fixed displaying aggregations names containing special characters

by Checkmk werks level 1

[//]: # (werk v2) # Aggregation visualization: Fixed displaying aggregations names containing special characters key | value ---------- | --- date | 2024-04-27T14:22:44+00:00 version | 2.3.0p1 class | fix edition | cre component | bi level | 1 compatible | yes

3 months, 3 weeks

[2.3.0] Checkmk Werk 16794 created: "checkgroup_parameters:if": Rename to "checkgroup_parameters:interfaces"

by Checkmk werks level 1

[//]: # (werk v2) # "checkgroup_parameters:if": Rename to "checkgroup_parameters:interfaces" key | value ---------- | --- date | 2024-04-26T11:27:20+00:00 version | 2.3.0b4 class | fix edition | cre component | checks level | 1 compatible | no This only affects you if you are configuring rules through the REST API. In order to make the "checkgroup_parameters:if" ruleset compliant with the new Ruleset API, it has been renamed to "checkgroup_parameters:interfaces". Any configuration inside Checkmk will be automatically updated, however any outside references to the old name will have to be adjusted manually.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16807 adapted: Ignore unknown "Disabled checks" during update config

by Checkmk werks level 1

Werk 16807 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Ignore unknown "Disabled checks" during update config key | value ---------- | --- date | 2024-04-24T12:25:30+00:00 version | 2.3.0p1 class | fix edition | cre component | checks level | 1 compatible | yes If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like ``` WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: , -| Rule nr: 1, Exception: ifoperstatus is not an allowed value) ``` These invalid values are ignored now. They do no harm and they are dropped upon editing the rule. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Ignore unknown "Disabled checks" during update config key | value ---------- | --- date | 2024-04-24T12:25:30+00:00 - version | 2.3.0b7 ? ^^ + version | 2.3.0p1 ? ^^ class | fix edition | cre component | checks level | 1 compatible | yes If users had disabled checks that have since been removed or are temporarily unavailable (due to disabled MKPs for instance), they would be prompted with a message like ``` WARNING: Invalid rule configuration detected (Ruleset: ignored_checks, Title: Disabled checks, Folder: , -| Rule nr: 1, Exception: ifoperstatus is not an allowed value) ``` These invalid values are ignored now. They do no harm and they are dropped upon editing the rule.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16811 adapted: Performance regression during config generation in 2.3.0b6

by Checkmk werks level 1

Werk 16811 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # Performance regression during config generation in 2.3.0b6 key | value ---------- | --- date | 2024-04-26T08:27:28+00:00 version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a performance regression introduced in Checkmk version 2.3.0b6. The introduced issue slowed the config generation down proportional to the number of monitored hosts. ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # Performance regression during config generation in 2.3.0b6 key | value ---------- | --- date | 2024-04-26T08:27:28+00:00 - version | 2.3.0p1 ? -- + version | 2.3.0 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a performance regression introduced in Checkmk version 2.3.0b6. The introduced issue slowed the config generation down proportional to the number of monitored hosts.

3 months, 3 weeks

[2.3.0] Checkmk Werk 16811 created: Performance regression during config generation in 2.3.0b6

by Checkmk werks level 1

[//]: # (werk v2) # Performance regression during config generation in 2.3.0b6 key | value ---------- | --- date | 2024-04-26T08:27:28+00:00 version | 2.3.0p1 class | fix edition | cre component | checks level | 1 compatible | yes This fixes a performance regression introduced in Checkmk version 2.3.0b6. The introduced issue slowed the config generation down proportional to the number of monitored hosts.

3 months, 3 weeks

← Newer
1
...
8
9
10
11
12
13
14
...
55
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2024