[//]: # (werk v2)
# New OderBy 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\OrderBy: name\Limit: 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
...
```
[//]: # (werk v2)
# omd restart: Exit Code is 2 on Failure
key | value
---------- | ---
date | 2024-01-26T13:27:19+00:00
version | 2.3.0b1
class | fix
edition | cre
component | omd
level | 1
compatible | yes
`omd restart` executes `omd start` and `omd stop`, both of which can terminate with exit code zero
or two. Previously, the exit code of these commands would be ignored. `omd restart` now reports the
worst exit code reported by the two commands.
[//]: # (werk v2)
# host_config: add inherited labels to effective attributes
key | value
---------- | ---
date | 2024-01-26T11:20:55+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Previously, when using the effective attributes query parameter with the
```
GET /objects/host_config/{host_name}
```
endpoint, only the labels of the current host have been returned.
Now all of the effective labels are aggregated and returned.
[//]: # (werk v2)
# Regression when obtaining mails from mailbox
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-21T13:17:42+00:00
level | 1
class | fix
component | checks
edition | cre
This regression exists since 2.2.0b1. Monitoring mails in your in box may have not been possible.
This is fixed now.
[//]: # (werk v2)
# ntopng integration: remove ntopng version support for versions older than 6.0
key | value
---------- | ---
date | 2024-02-22T13:18:29+00:00
version | 2.4.0b1
class | fix
edition | cee
component | ntopng_integration
level | 1
compatible | no
Since Werk 16479 the ntopng integration was compatible with both ntopng versions newer than 6.0
and older than 6.0.
With this change the ntopng integration no longer supports version older than 6.0.
Werk 16085 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
- (4/5)
Werk 16085 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
(4/5)
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
- (3/5)
? ^
+ (4/5)
? ^
Werk 16085 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
(3/5)
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
- (2/5)
? ^
+ (3/5)
? ^
Werk 16085 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
(2/5)
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
- (1/5)
? ^
+ (2/5)
? ^
[//]: # (werk v2)
# Agent Updater: Better detection of underlying platform
key | value
---------- | ---
date | 2024-02-21T10:36:36+00:00
version | 2.4.0b1
class | fix
edition | cee
component | agents
level | 1
compatible | yes
Previously, the agent updater used to detect the underlying platform,
in terms of the combination of OS and package manager (e.g., Linux + RPM),
automatically by scanning for certrain directories.
As multiple package managers may be available on one system, this sometimes
lead to unexpected behavior on agent updates when the update mechanism decided
to switch to a different platform.
Now, the platform will be specified by a file that comes with the agent installation,
and the agent updater will rely on this static information instead of the dynamic detection.
(1/5)