[//]: # (werk v2)
# Improve main menu keyboard navigation
key | value
---------- | ---
date | 2024-01-16T11:21:43+00:00
version | 2.3.0b1
class | feature
edition | cre
component | multisite
level | 2
compatible | yes
The main menu of the UI has now more extended support for keyboard navigation.
You can open up the menus with the following key combinations:
* Monitoring: `ALT + m`
* Setup: `ALT + s`
* Customize: `ALT + c`
The search field is automatically focussed (as before), you can directly insert
your search term. By using `TAB` you can navigate the search results and confirm
your choice with `ENTER`.
Pressing `ESC` for the first time clears the current search term. A second `ESC`
closes the open menu.
Utilizing the workflow can make navigating to the desired pages in Checkmk much
faster.
Title: snmp inline backend ignores no Access error
Class: fix
Compatible: compat
Component: core
Date: 1697714323
Edition: cee
Level: 1
Version: 2.3.0b1
Snmp walks that result in a "no Access" error are now be treated as if the walk
returned no data. A debug log entry informs the user about this.
Werk 14859 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Event Console: Fix The EC always activates the config written by the previous activation.
key | value
---------- | ---
date | 2024-01-16T14:13:44+00:00
version | 2.3.0b1
class | fix
edition | cre
component | ec
level | 2
compatible | yes
The bug was introduced by the werk: [#16012](https://checkmk.com/werk/16012) in version 2.2.0p18.
A workaround would be: make a trivial change to the rules/rule packs (edit description)
and activate the changes. Or reload the EC manually after the initial reload to apply the correct config.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Event Console: Fix events not created after initial activate changes
+ # Event Console: Fix The EC always activates the config written by the previous activation.
key | value
---------- | ---
date | 2024-01-16T14:13:44+00:00
version | 2.3.0b1
class | fix
- edition | cee
? -
+ edition | cre
? +
component | ec
- level | 1
? ^
+ level | 2
? ^
compatible | yes
- The bug was introduced by the werk: [#16012](https://checkmk.com/werk/16012)
+ The bug was introduced by the werk: [#16012](https://checkmk.com/werk/16012) in version 2.2.0p18.
? +++++++++++++++++++++
+ A workaround would be: make a trivial change to the rules/rule packs (edit description)
+ and activate the changes. Or reload the EC manually after the initial reload to apply the correct config.
-
[//]: # (werk v2)
# Event Console: Fix events not created after initial activate changes
key | value
---------- | ---
date | 2024-01-16T14:13:44+00:00
version | 2.3.0b1
class | fix
edition | cee
component | ec
level | 1
compatible | yes
The bug was introduced by the werk: [#16012](https://checkmk.com/werk/16012)
Werk 16025 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
Version: 2.2.0p19
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
------------------------------------<diff>-------------------------------------------
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
- Version: 2.2.0p17
? ^
+ Version: 2.2.0p19
? ^
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
Version: 2.2.0p17
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
Title: mk_tsm: Fix export: =: is not an identifier
Class: fix
Compatible: compat
Component: checks
Date: 1705329209
Edition: cre
Knowledge: doc
Level: 1
Version: 2.3.0b1
Since Werk 16273 `eval` is no longer used to create the required environment.
In some setups, the following error occurs.
```
export: =: is not an identifier
```
With this Werk the error is fixed.
The error occured, if the ouput of `get_dsmserv_processes` consisted of a single linebreak.
[//]: # (werk v2)
# ucd_disk: fs_size, fs_used and fs_free have wrongly scaled values in performance graphs
key | value
---------- | ---
date | 2024-01-15T13:22:37+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
For `ucd_disk` a performance value translation had been missing, fixed by this change.
Title: Update PHP version in SLES15SP3 from 7 to 8
Class: fix
Compatible: incomp
Component: rpm
Date: 1701254497
Edition: cre
Level: 2
Version: 2.3.0b1
Checkmk was shipped with a dependency to PHP7 for SLES15SP3. Since PHP7 is
part of the legacy module, this Werk updates the dependency from PHP7 to PHP8.
As SLES only allows one version of PHP to be installed, the following steps
will uninstall PHP7 from the system and install the new version of Checkmk
with PHP8. Be aware that this procedure updates PHP from version 7 to 8 for the whole OS. In case you run additional PHP applications next to Checkmk, the update will also affect them.
Run the following commands to perform the update to the new Checkmk version:
* add SLES-15SP4 repo to get PHP8 with <tt>zypper addrepo https://updates.suse.com/SUSE/Products/SLE-BCI/15-SP4/x86_64/product/ sles15sp4</tt>
* install the new Checkmk version with <tt>zypper install NEW_CHECKMK.rpm</tt>
* Zypper will now complain about a conflict with several PHP packages and asks you to select a solution. There, select <tt>solution 1</tt> to confirm the deinstallation of the current Checkmk version, the PHP7 modules and to continue with the installation
* confirm the installation of the new Checkmk version and PHP8 with <tt>yes</tt>
* removing the existing Checkmk version will throw an error like `Site <SITENAME> is still using this version! Removal of <OLD_CHECKMK>(@System) failed:`, proceed by choosing <tt>ignore</tt> which creates a inconsistent state for the old Checkmk version package, which we will resolve in a later step.
* PHP7 will be removed and PHP8 gets installed
* change to the site user with <tt>omd su SITE_NAME</tt>
* stop the site with <tt>omd stop</tt>
* perform the update to the new Checkmk version with <tt>omd update</tt>, select <tt>Update</tt> at the user prompt
* in case further prompts regarding wrong permissions of BUILD files appear, choose the default value with <tt>d</tt>
* start the site again with <tt>omd start</tt>
* exit from the site user
* list all installed Checkmk version with <tt>omd versions</tt>
* finally remove the old Checkmk installation with <tt>zypper remove OLD_CHECKMK</tt>
[//]: # (werk v2)
# mem_win: Base prediction on original measurement
key | value
---------- | ---
date | 2024-01-11T22:47:00+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This only affects users that monitor the memory usage of Windows hosts using both averaging and predictive levels.
The prediction is now based on the unaveraged original value, potentially leading to a slightly larger standard deviation.
The resulting levels are still applied to the averaged value, if averaging is configured.