Title: ucd_disk: fs_size, fs_used and fs_free have wrongly scaled values in performance graphs
Class: fix
Compatible: compat
Component: checks
Date: 1705324957
Edition: cre
Level: 1
Version: 2.2.0p19
For <code>ucd_disk</code> a performance value translation had been missing, fixed by this change.
Title: mk_tsm: Fix export: =: is not an identifier
Class: fix
Compatible: compat
Component: checks
Date: 1705329209
Edition: cre
Knowledge: doc
Level: 1
State: unknown
Version: 2.2.0p19
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)
# user_config: add verification for contact groups and locked attributes
key | value
---------- | ---
date | 2024-01-16T14:42:21+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
This werk introduces two changes:
* it now verifies for create & edit if the provided contact groups actually exist
* it verifies that for an edit request, locked attributes are not being modified
[//]: # (werk v2)
# user_config: verify contact group existence when creating or editing user
key | value
---------- | ---
date | 2024-01-11T13:32:35+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
[//]: # (werk v2)
# revert_changes: internal changes can be reverted only if the user has the correct permission
key | value
---------- | ---
date | 2024-01-17T11:41:59+00:00
version | 2.3.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
Changes made by the checkmk internal user can now only be reverted when the
logged-in user has the permission "Discard foreign changes".
[//]: # (werk v2)
# Support Diagnostics: Also add the latest Crash Dumps to the SD Dump
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2023-09-27T16:54:11+00:00
level | 1
class | feature
component | setup
edition | cre
For each category of crash dumps (base, check, ec, gui, rest_api, section), add the latest dump
to the Support Diagnostics dump.
[//]: # (werk v2)
# Fix missing event console rules after site update
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-17T09:18:22+00:00
level | 1
class | fix
component | ec
edition | cee
With werk 16012 the event console rules are filtered ond saved to the location
var/mkeventd/active_config during activate changes.
This werk fixes the missing procedure while updating to a new Checkmk version.
[//]: # (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.
-