[//]: # (werk v2)
# Read-only internal folder name when editing folders
key | value
---------- | ---
date | 2024-03-20T08:45:21+00:00
version | 2.3.0b4
class | fix
edition | cre
component | wato
level | 1
compatible | yes
When disabling the "Hide internal folder names in Setup" setting, the internal
name must be set by the user when creating folders. Previously, the field was
still modifiable when editing the folder properties, however no changes to it
were saved.
This werk now marks the field as read only when editing the folder properties.
[//]: # (werk v2)
# dns: Reintroduce macro replacement in 'Expected DNS answers' config
key | value
---------- | ---
date | 2024-03-20T08:49:31+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
With version 2.3.0b1, the macros in the 'Expected DNS answers' field of 'Check DNS service'
were no longer replaced. This change reintroduces macro replacement.
[//]: # (werk v2)
# postfix: Fix Postfix status monitoring for agents run in Docker
key | value
---------- | ---
compatible | yes
version | 2.3.0b4
date | 2024-03-13T09:57:01+00:00
level | 1
class | fix
component | checks
edition | cre
Previously, Checkmk agent used the data from /proc to determine if Postfix instance is running.
Since docker containers don't have permissions to read /proc, the agent always reported
the Postfix instance as 'not running'.
This resulted in CRIT 'Postfix status' service even if Postfix instance was running correctly.
[//]: # (werk v2)
# REST API: Fix httpie examples
key | value
---------- | ---
date | 2024-03-20T12:51:32+00:00
version | 2.3.0b4
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Some httpie examples had a backslash at the end of the last line causing
these examples to fail when executed. This Werk fixes the way REST API
examples are generated to prevent backslashes at the end of the last line.
[//]: # (werk v2)
# size_trend: Treat negative free space as 0 in all cases
key | value
---------- | ---
compatible | yes
version | 2.3.0b4
date | 2024-03-20T10:04:09+00:00
level | 1
class | fix
component | checks
edition | cre
Before the version 2.2.0p21, 'Time left until full' was reported to be 0 in case of
devices reporting negative free space.
With werk 16330, we stopped reporting the metric in case of very small size changes
because it lead to infinite values. With this change the behavior was unintentionally
also changed for negative free space values.
This werk restores the same functionality in case of negative free space.
Werk 16646 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Nagios / CRE: Error precompiling checks: Cannot find check file
key | value
---------- | ---
date | 2024-03-18T20:52:03+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a regression introduced in Checkmk 2.3.0b1 for Nagios / CRE users.
The reported error during config creation was
"Error precompiling checks for host \<HOST\>: Cannot find check file needed for \<agent_name\>".
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Nagios / CRE: Error precompiling checks: Cannot find check file
key | value
---------- | ---
date | 2024-03-18T20:52:03+00:00
- version | 2.3.0b3
? ^
+ version | 2.3.0b4
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This fixes a regression introduced in Checkmk 2.3.0b1 for Nagios / CRE users.
The reported error during config creation was
"Error precompiling checks for host \<HOST\>: Cannot find check file needed for \<agent_name\>".
Werk 16630 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Prevent check_mail crash for "Move to subfolder" option
key | value
---------- | ---
date | 2024-03-18T09:19:03+00:00
version | 2.3.0b4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The active check check_mail can be configured to move mail messages from the inbox to a subfolder via the options "Forward mails as events to Event Console" > "Cleanup messages" > "Move to subfolder".
For IMAP the copying of mails crashed when there were no mails available in the inbox.
This is fixed to skipping the copy command in case there are no mails given.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Prevent check_mail crash for "Move to subfolder" option
key | value
---------- | ---
date | 2024-03-18T09:19:03+00:00
- version | 2.3.0b3
? ^
+ version | 2.3.0b4
? ^
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The active check check_mail can be configured to move mail messages from the inbox to a subfolder via the options "Forward mails as events to Event Console" > "Cleanup messages" > "Move to subfolder".
For IMAP the copying of mails crashed when there were no mails available in the inbox.
This is fixed to skipping the copy command in case there are no mails given.
[//]: # (werk v2)
# Check SQL: Allow to configure port via custom macros
key | value
---------- | ---
date | 2024-03-15T13:24:34+00:00
version | 2.3.0b4
class | feature
edition | cre
component | checks
level | 1
compatible | yes
In the ruleset _"Check SQL Database"_ you can now configure the port using
macros.
Werk 16149 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# New OrderBy header in livestatus
key | value
---------- | ---
date | 2024-01-29T10:12:24+00:00
version | 2.3.0b1
class | feature
edition | cre
component | livestatus
level | 1
compatible | yes
We provide a new header for livestatus that returns the rows in
sorted order.
For example, to sort host names in descending order
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name desc'
zhost
yhost
xhost
...
```
in ascending order
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name asc'
ahost
bhost
...
```
or, alternatively without `asc`,
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name'
ahost
bhost
...
```
The `OrderBy` header can be combined with the `Limit` header to
limit the number of results as expected.
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name\nLimit: 1'
ahost
```
Furthermore, it is possible to sort on dictionary keys with the
following syntax
```
$ lq << EOF
GET services
Columns: host_name description performance_data
OrderBy: performance_data.user_time
EOF
...
```
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # New OderBy header in livestatus
+ # New OrderBy header in livestatus
? +
key | value
---------- | ---
date | 2024-01-29T10:12:24+00:00
version | 2.3.0b1
class | feature
edition | cre
component | livestatus
level | 1
compatible | yes
We provide a new header for livestatus that returns the rows in
sorted order.
For example, to sort host names in descending order
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name desc'
zhost
yhost
xhost
...
```
in ascending order
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name asc'
ahost
bhost
...
```
or, alternatively without `asc`,
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name'
ahost
bhost
...
```
The `OrderBy` header can be combined with the `Limit` header to
limit the number of results as expected.
```
$ lq 'GET hosts\nColumns: name\nOrderBy: name\nLimit: 1'
ahost
```
Furthermore, it is possible to sort on dictionary keys with the
following syntax
```
$ lq << EOF
GET services
Columns: host_name description performance_data
OrderBy: performance_data.user_time
EOF
...
```