Checkmk werks level1 November 2023

checkmk-werks-lvl1@lists.checkmk.com

1 participants
219 discussions

[2.2.0] Checkmk Werk 16300 adapted: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs

by Checkmk werks level 1

Werk 16300 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.2.0p16 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data. ------------------------------------<diff>------------------------------------------- - Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs + Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs ? + Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.2.0p16 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data.

9 months, 3 weeks

[2.2.0] Checkmk Werk 16300 created: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs

by Checkmk werks level 1

Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.2.0p16 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data.

9 months, 3 weeks

[2.2.0] Checkmk Werk 16290 created: Limit login to single session: modify sessions lookup to enable the option

by Checkmk werks level 1

Title: Limit login to single session: modify sessions lookup to enable the option Class: fix Compatible: compat Component: wato Date: 1700659867 Edition: cre Level: 1 Version: 2.2.0p16 Prior to this werk, the user got logged out from the UI as soon as the global setting option 'Limit login to single session at a time' was enabled. This was due to the fact that the active sessions lookup returned an empty result which prevented any further notification. This werk fixes this behaviour and reinstates the behaviour of the 2.1 version.

9 months, 3 weeks

[2.2.0] Checkmk Werk 15977 deleted: db2_backup: Correct timezone difference for last backup date

by Checkmk werks level 1

Werk 15977 was deleted. The following Werk is no longer relevant. Title: db2_backup: Correct timezone difference for last backup date Class: fix Compatible: compat Component: checks Date: 1697190433 Edition: cre Level: 1 Version: 2.2.0p15 This werk is relevant for users monitoring the age of the last backup time of db2 databases in different timezones. The date/time of the last backup of a db2 database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone. When using different timezones, this leads to incorrect values for "Time since last backup". The db2 agent plugin will now store the time in UTC and the db2_backup check will interpret the time accordingly. You will need to update the agent mk_db2.linux or mk_db2.aix to receive the corrected times.

9 months, 3 weeks

[2.2.0] Checkmk Werk 15976 deleted: mssql_backup: Correct timezone difference for last backup date

by Checkmk werks level 1

Werk 15976 was deleted. The following Werk is no longer relevant. Title: mssql_backup: Correct timezone difference for last backup date Class: fix Compatible: compat Component: checks Date: 1696949130 Edition: cre Knowledge: doc Level: 1 State: unknown Version: 2.2.0p15 This werk is relevant for users monitoring the age of the last backup time of mssql databases in different timezones. The date/time of the last backup of a mssql database is currently stored in local host time without the information about the host timezone. When this time is used to check the age of the last backup, it is interpreted in the Checkmk server timezone. When using different timezones, this leads to incorrect values for "Age of last database backup" and if the age is negative, in newer Checkmk versions to the warning "Cannot reasonably calculate time since last backup (hosts time running ahead)". The mssql agent plugin will now store the time in UTC and the mssql_backup check will interpret the time accordingly. You will need to update the agent plugin mssql.vbs to receive the corrected times.

9 months, 3 weeks

[2.2.0] Checkmk Werk 16231 created: Cease to provide builds for Ubuntu 22.10 (Kinetic Kudu)

by Checkmk werks level 1

Title: Cease to provide builds for Ubuntu 22.10 (Kinetic Kudu) Class: fix Compatible: incomp Component: omd Date: 1700665071 Edition: cre Level: 1 Version: 2.2.0p15 With this werk, we cease to deliver builds for Ubuntu 22.10. Since Ubuntu 22.10 is out of support since August 2023, it is necessary to upgrade to Ubuntu 23.04 or 23.10 before installing upcoming Checkmk builds.

9 months, 3 weeks

[2.3.0] Checkmk Werk 15922 created: cisco_meraki_org_sensor_readings: Checks for battery and humidity percentage added

by Checkmk werks level 1

Title: cisco_meraki_org_sensor_readings: Checks for battery and humidity percentage added Class: feature Compatible: compat Component: checks Date: 1700737053 Edition: cre Level: 1 Version: 2.3.0b1

9 months, 3 weeks

[2.3.0] Checkmk Werk 16300 adapted: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs

by Checkmk werks level 1

Werk 16300 was adapted. The following is the new Werk, a diff is shown at the end of the message. Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.3.0b1 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data. ------------------------------------<diff>------------------------------------------- - Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs + Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0</tt> in forecast graphs ? + Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.3.0b1 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data.

9 months, 3 weeks

[2.3.0] Checkmk Werk 16228 created: Enable update as site user due incompatible python versions

by Checkmk werks level 1

Title: Enable update as site user due incompatible python versions Class: fix Compatible: compat Component: omd Date: 1699525492 Edition: cre Level: 1 Version: 2.3.0b1 This werk is relevant for you in case you've been using <tt>omd -V {version} update</tt> as site user. Due to the update of the Python version from 3.11.2 to 3.11.5 with 2.2.0p13, we needed to introduce a fix in order to avoid the following issue: C+: Traceback (most recent call last): File "/omd/versions/2.2.0p13.cee/bin/omd", line 60, in <module> import omdlib.main File "/omd/versions/2.2.0p13.cee/lib/python3/omdlib/main.py", line 36, in <module> import random File "/omd/versions/2.2.0p13.cee/lib/python3.11/random.py", line 49, in <module> from math import log as _log, exp as _exp, pi as _pi, e as _e, ceil as _ceil ImportError: /omd/versions/2.2.0p13.cee/lib/python3.11/lib-dynload/math.cpython-311-x86_64-linux-gnu.so: undefined symbol: _PyModule_Add C-: However, this fix introduced another issue with the release of 2.2.0p13, that's why we had to withdraw 2.2.0p13 and release 2.2.0p14 which addressed both issues.

9 months, 3 weeks

[2.3.0] Checkmk Werk 16300 created: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs

by Checkmk werks level 1

Title: Revert werk #16150 and fix <tt>IndexError: boolean index did not match indexed array along dimension 0<tt> in forecast graphs Class: fix Compatible: compat Component: metrics Date: 1700760668 Edition: cee Level: 1 Version: 2.3.0b1 This change reverts werk #16150, since this werk made forecast graphs basically unusable. Furthermore, this change fixes the error mentioned above. This error occurred when computing a forecast based on constant and incomplete input data.

9 months, 3 weeks

← Newer
1
2
3
4
5
6
7
8
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 November 2023