[//]: # (werk v2)
# notification_rules: custom plugins now created correctly when using the REST-API
key | value
---------- | ---
date | 2024-01-22T08:18:31+00:00
version | 2.3.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Previous to this werk, when creating a notification rule with a custom
plugin via the rest-api, the parameters were not being shown in the UI
as expected. The reason being, an incorrect format being saved to file.
This werk addresses this issue by correcting the format being saved to
file.
[//]: # (werk v2)
# BGP Peer State Mapping: add connect state
key | value
---------- | ---
date | 2024-01-30T13:09:08+00:00
version | 2.3.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
BGP Peer States can be in "connect". This state was missing in checkmk and thus
the service was in "UNKNOWN" state.
[//]: # (werk v2)
# Sets deprecation age for mails sent by check_mail_loop from 24h to 2h
key | value
---------- | ---
date | 2024-01-30T12:49:59+00:00
version | 2.3.0b1
class | feature
edition | cre
component | checks
level | 1
compatible | yes
Mails sent by `check_mail_loop` had been deprecated only after 24h, which potentially resulted
in thousands of mails in circumstances when sent mails could not be processed for whatever
reasons.
This change lowers this age to 2h resulting in 'only' 120 mails (for this active check being
executed every minute).
[//]: # (werk v2)
# BI: fixed exception in check if aggregation was in state PENDING
key | value
---------- | ---
date | 2024-01-30T08:17:38+00:00
version | 2.3.0b1
class | fix
edition | cre
component | bi
level | 1
compatible | yes
[//]: # (werk v2)
# NetApp: addition of datasource program and check plugins for NetApp ONTAP
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-29T12:15:27+00:00
level | 1
class | feature
component | checks
edition | cre
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
[//]: # (werk v2)
# mcafee_webgateway: Services not being discovered
key | value
---------- | ---
compatible | yes
version | 2.3.0b1
date | 2024-01-29T10:17:43+00:00
level | 1
class | fix
component | checks
edition | cre
Some mcafee services were not discovered because of the detection criteria.
This has now been fixed by using the 'OBJECTID' for the detection.
[//]: # (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.