Title: azure_vm_network_io: KeyError (total_Network_In_Total)
Class: fix
Compatible: compat
Component: checks
Date: 1707142294
Edition: cre
Level: 1
Version: 2.2.0p22
The Microsoft Azure API sometimes omits the metrics total_Network_In_Total and
total_Network_Out_Total. The check plugin azure_vm_network_io now omits computations based on these
metrics rather than crashing.
Title: Respect sort index for listed dashboards in page menu
Class: fix
Compatible: compat
Component: multisite
Date: 1707138304
Edition: cre
Level: 1
Version: 2.2.0p22
The page menu "Dashboards" in dashboards listed all other available dashboards
in a random order. The defined sort index of each dashboard is now respected.
Werk 16149 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# New OderBy 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
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\OrderBy: name\Limit: 1'
+ $ 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
...
```
[//]: # (werk v2)
# azure_vm_network_io: KeyError (total_Network_In_Total)
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-02-05T14:11:34+00:00
level | 1
class | fix
component | checks
edition | cre
The Microsoft Azure API sometimes omits the metrics total_Network_In_Total and
total_Network_Out_Total. The check plugin azure_vm_network_io now omits computations based on these
metrics rather than crashing.
[//]: # (werk v2)
# Respect sort index for listed dashboards in page menu
key | value
---------- | ---
date | 2024-02-05T13:05:04+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
The page menu "Dashboards" in dashboards listed all other available dashboards
in a random order. The defined sort index of each dashboard is now respected.
Title: if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description
Class: fix
Compatible: incomp
Component: checks
Date: 1706806081
Edition: cre
Level: 1
Version: 2.1.0p40
Sometimes the Lancom routers don't provide a name. During data parsing this caused the description to be left as an empty string.
As a result of that, when the router description was configured to be used for the Service Desciption, the discovery did not work properly.
This has now been fixed by having a fallback mechanism. If the router name is not present, the router description will be used.
Because of the change, the user is required to execute the service discovery again in order to discover any new services.
As well as get rid of any vanished services.
Title: omd start mkeventd: Error Code of Event Daemon
Class: fix
Compatible: compat
Component: omd
Date: 1706877168
Edition: cre
Level: 1
Version: 2.1.0p39
The command <code>omd start mkeventd</code> starts the event daemon. Previously, any exit code produced
by this daemon would be ignored. Now, if the exit code is non-zero, then the message <code>Failed</code> is
shown and the command <code>omd start mkeventd</code> exits with error code 2.
Title: if_lancom: Switch port discovery does not work for Lancom routers when the router description is configured to be used for the Service Description
Class: fix
Compatible: incomp
Component: checks
Date: 1706806081
Edition: cre
Level: 1
Version: 2.2.0p22
Sometimes the Lancom routers don't provide a name. During data parsing this caused the description to be left as an empty string.
As a result of that, when the router description was configured to be used for the Service Desciption, the discovery did not work properly.
This has now been fixed by having a fallback mechanism. If the router name is not present, the router description will be used.
Because of the change, the user is required to execute the service discovery again in order to discover any new services.
As well as get rid of any vanished services.
Title: Hide private topics in dropdowns
Class: fix
Compatible: compat
Component: multisite
Date: 1706774864
Edition: cre
Level: 1
Version: 2.2.0p22
Private topics were showing up in dropdowns (e.g. when editing dashboards).
Now they are hidden if the user does not have permissions for them.
Title: Fix topics being falsely shown as public
Class: fix
Compatible: incomp
Component: multisite
Date: 1706774499
Edition: cre
Level: 1
Version: 2.2.0p22
Previously, pagetypes (bookmarks, custom graphs, topics etc.) were falsely
handled as public, rather than private. Items published only to specific groups
are not affected and were handled correctly.
This change may cause users to no longer see public overwrites by admins for
example. Please ensure your permissions and publish states are configured
correctly.