[//]: # (werk v2)
# Read-only internal folder name when editing folders
key | value
---------- | ---
date | 2024-03-20T08:45:21+00:00
version | 2.4.0b1
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)
# size_trend: Treat negative free space as 0 in all cases
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
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 v2)
# REST API: Fix httpie examples
key | value
---------- | ---
date | 2024-03-20T12:51:32+00:00
version | 2.4.0b1
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)
# dns: Reintroduce macro replacement in 'Expected DNS answers' config
key | value
---------- | ---
date | 2024-03-20T08:49:31+00:00
version | 2.4.0b1
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)
# Check SQL: Allow to configure port via custom macros
key | value
---------- | ---
date | 2024-03-15T13:24:34+00:00
version | 2.4.0b1
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 v2)
# Terminate all GUI sessions during update
key | value
---------- | ---
date | 2024-03-15T15:16:28+00:00
version | 2.4.0b1
class | feature
edition | cre
component | wato
level | 1
compatible | yes
By default a GUI session is terminated after 90 minutes of inactivity (Configurable via global setting **Session management**).
A user could therefore start a session and e.g. start configuring a complex check and while doing something other (e.g. researching some options) the site could be updated.
If the user does not interact with the site in that period the user won't notice that the site was updated.
Since updates might change some behaviour the session might not work as intended.
Therefore during an update all sessions are now terminated.
This will cause users to re-authenticate after a site update.
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.4.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.4.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
...
```
Title: quantum_libsmall_*: Improve SNMP detection
Class: fix
Compatible: compat
Component: checks
Date: 1709035896
Edition: cre
Level: 1
Version: 2.1.0p41
Currently the SNMP detection for <code>quantum_libsmall_status</code> and <code>quantum_libsmall_door</code> checks if "linux" and "library" are contained in the sysDescr and sysLocation OIDs. To make the detection more reliable, the sysObjectID is checked against the linux object identifier and the libraryProductName .1.3.6.1.4.1.3697.1.10.10.1.10.0 against "Quantum Small Library Product".
Title: Virtual host tree links work for more than three host tag groups
Class: fix
Compatible: compat
Component: multisite
Date: 1710494682
Edition: cre
Level: 1
Version: 2.2.0p24
A virtual host tree (Setup > General > Global settings > User interface > Virtual host trees) can be configured with more than three host tag tree levels. Yet, the corresponding views that are linked to from the sidebar element "Virtual host trees" were not able to display more than three rows in the "Host tags" filter and thus only filtered for the first three.
This is fixed. A virtual host tree link as described above now leads to a properly filtered view with all the given host tag filters shown in the filter popup.