Werk 16047 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Changed host labels for Azure Resource Groups and Virtual Machine
key | value
---------- | ---
date | 2024-01-26T12:20:23+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | no
This werk affects users who use the tags of Azure Resource Groups or Virtual Machines (if monitored as hosts) as host labels in Checkmk.
The host labels are renamed from the original Azure format "{key}":"{value}" to "cmk/azure/tag/{key}":"{value}" in order to stay consistent with other host labels and to avoid overwriting existing Checkmk labels.
Additionally, label keys and values are now validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So a former label "label:key":"" will now be shown as "label_key":"true".
The old labels will be removed in version 2.4.0.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
- # Changed host labels for Azure Resource Groups and Virutal Machines
? - -
+ # Changed host labels for Azure Resource Groups and Virtual Machine
? +
key | value
---------- | ---
date | 2024-01-26T12:20:23+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | no
This werk affects users who use the tags of Azure Resource Groups or Virtual Machines (if monitored as hosts) as host labels in Checkmk.
The host labels are renamed from the original Azure format "{key}":"{value}" to "cmk/azure/tag/{key}":"{value}" in order to stay consistent with other host labels and to avoid overwriting existing Checkmk labels.
Additionally, label keys and values are now validated to 1) not hold empty values - empty values are replaced by "true" and 2) not contain colons (":") - colons are replaced by underscores ("_"). So a former label "label:key":"" will now be shown as "label_key":"true".
The old labels will be removed in version 2.4.0.
[//]: # (werk v2)
# netapp_ontap_vs_traffic: add missing svm_nfs_v3 counters
key | value
---------- | ---
date | 2024-02-05T07:51:38+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This werk adds two missing counters to the mentioned plugin, the counters `svm_nfs_v3:read_ops` and `svm_nfs_v3:write_ops`.
[//]: # (werk v2)
# service discovery: introduce functionality to fetch job status from remote sites
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-01-29T10:23:24+00:00
level | 1
class | fix
component | rest-api
edition | cre
Prior to this werk, the service discovery endpoints were restricted to the local
service discovery background job. This resulted in the following endpoints being
restricted to local setups only:
* Show the last service discovery background job on a host
* Wait for service discovery completion
This werk fixes this and now also supports distributed monitoring setups. To benefit
from this change both the central site as well the remote sites need to be updated
to the werk's version. This change does not affect local only setups.
Werk 16324 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# NetApp: addition of datasource program and check plugins for NetApp ONTAP
key | value
---------- | ---
date | 2024-01-29T12:15:27+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
Since NetApp has discontinued support for their old API this werk adds datasource program and check plugins for the new NetApp ONTAP REST API.
However, the new API does not provide certain metrics that were available in the old API. As a result, the new check plugins have been modified accordingly.
The plugins that have been migrated with this werk are the ones that monitor:
- NetApp aggregates
- NetApp node's CPUs
- NetApp disks
- NetApp sensors of environment and shelves
- NetApp node's fans
- NetApp node's interfaces
- NetApp LUNs
- NetApp node's ports
- NetApp power supply units
- NetApp volumes (and snapshots)
- NetApp (SVMs) Storage Virtual Machine's (formerly called "vservers”) traffic and status
These plugins and metrics are under development:
- NetApp snapvault
- NetApp qtree quota
- NetApp FCP
- NetApp (SVMs) Storage Virtual Machine's (formerly called "vservers”)
- Nfsv3_read_ios (read ops)
- Nfsv3_write_ios (write ops)
Here is a list of missing metrics and plugins as the corresponding data cannot be found in the new NetApp API:
- NetApp Disk Summary
- Parity disks
- Total number of disks type data
- Total number of disks type parity
- Traffic SVM (formerly vServer)
- Nfsv4_read_ios (read ops)
- Nfsv4_write_ios (write ops)
- System time
- Missing service
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# NetApp: addition of datasource program and check plugins for NetApp ONTAP
key | value
---------- | ---
date | 2024-01-29T12:15:27+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
Since NetApp has discontinued support for their old API this werk adds datasource program and check plugins for the new NetApp ONTAP REST API.
However, the new API does not provide certain metrics that were available in the old API. As a result, the new check plugins have been modified accordingly.
The plugins that have been migrated with this werk are the ones that monitor:
- NetApp aggregates
- NetApp node's CPUs
- NetApp disks
- NetApp sensors of environment and shelves
- NetApp node's fans
- NetApp node's interfaces
- NetApp LUNs
- NetApp node's ports
- NetApp power supply units
- NetApp volumes (and snapshots)
- NetApp (SVMs) Storage Virtual Machine's (formerly called "vservers”) traffic and status
+ These plugins and metrics are under development:
+ - NetApp snapvault
+ - NetApp qtree quota
+ - NetApp FCP
+ - NetApp (SVMs) Storage Virtual Machine's (formerly called "vservers”)
+ - Nfsv3_read_ios (read ops)
+ - Nfsv3_write_ios (write ops)
+
+ Here is a list of missing metrics and plugins as the corresponding data cannot be found in the new NetApp API:
+ - NetApp Disk Summary
+ - Parity disks
+ - Total number of disks type data
+ - Total number of disks type parity
+ - Traffic SVM (formerly vServer)
+ - Nfsv4_read_ios (read ops)
+ - Nfsv4_write_ios (write ops)
+ - System time
+ - Missing service
[//]: # (werk v2)
# NetApp: new addition of datasource program and check plugins for NetApp ONTAP
key | value
---------- | ---
date | 2024-02-05T12:36:23+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
With this werk the last NetApp check plugins have been migrated for the new NetApp ONTAP REST API.
The new migrated plugins are:
- NetApp snapvault
- NetApp qtree quota
- NetApp FCP
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.