[//]: # (werk v2)
# seh_ports: support new OIDs from updated sehMIB v2.5
key | value
---------- | ---
date | 2024-05-15T05:36:17+00:00
version | 2.3.0p3
class | feature
edition | cre
component | checks
level | 1
compatible | yes
The `seh_ports` check was unable to deal with newer devices sending SNMP data based on
SEH-MIB v2.5 (2023.10.31) (compared to the already handled format SEH-PSRV-MIB v1.167.
This change makes `seh_ports` deal with the new format next to the old one.
[//]: # (werk v2)
# FIX mongodb_replica_set: compatibility with pymongo 3
key | value
---------- | ---
date | 2024-05-15T09:54:03+00:00
version | 2.3.0p3
class | fix
edition | cre
component | checks
level | 1
compatible | yes
[Werk #16174](https://checkmk.com/werk/16174) introduced a regression: If the
checkmk agent plugin is running with pymongo version 3 the replication lag time
stamp is interpreted as seconds, but its actually milliseconds. This results in
errors like `ValueError (year 56319 is out of range)`.
The check is now compatible with pymongo version 3 and 4.
[//]: # (werk v2)
# SNMP: Fix missing data error when using 'Fetch intervals for SNMP sections'
key | value
---------- | ---
date | 2024-05-14T04:33:16+00:00
version | 2.3.0p3
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Users using the `Fetch intervals for SNMP sections` rule, would occasionally
get a missing data error, after which the monitoring would return back to normal.
The cause was SNMP section becoming expired during the checking. The problem is
fixed by using the last fetched section data instead.
[//]: # (werk v2)
# Add "Update service labels" option to service_discovery endpoint
key | value
---------- | ---
date | 2024-05-15T07:27:47+00:00
version | 2.3.0p3
class | feature
edition | cre
component | rest-api
level | 1
compatible | yes
[Werk 16466](https://checkmk.com/werk/16466) introduced the option to update
discovered service labels.
This feature was missing for the REST API service discovery endpoint.
This can now be done by using the `only_service_labels` mode for the
`/domain-types/service_discovery_run/actions/start/invoke` endpoint
[//]: # (werk v2)
# Show correct height of dashboards
key | value
---------- | ---
date | 2024-05-15T14:44:02+00:00
version | 2.3.0p3
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Dashboards were rendered with a to large height, leading to a scrollbar and
missing last lines.
[//]: # (werk v2)
# License usage history which is older than five days does not block activation anymore
key | value
---------- | ---
date | 2024-05-14T15:15:27+00:00
version | 2.3.0p3
class | fix
edition | cce
component | wato
level | 1
compatible | yes
If the license usage history is older than five days then activation may be
blocked. We removed this restriction and show a warning instead. If you run
into this issue the situation can be solved by executing this command as site
user:
```
cmk-update-license-usage --force
```
[//]: # (werk v2)
# Interface checks for Windows hosts: Fix broad- and non-unicast packets mixup
key | value
---------- | ---
date | 2024-05-14T12:41:33+00:00
version | 2.3.0p3
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Before this werk, for Windows hosts, the interface check reported non-unicast packets as broadcast
packets. As a side-effect, depending on the configuration, other rates such as the error rates,
might not have been reported. This happened if percentual levels were configured, which is the
default for error rates.
[//]: # (werk v2)
# Ensure correct sort order in "Site" filter
key | value
---------- | ---
compatible | yes
version | 2.3.0p3
date | 2024-05-15T07:18:38+00:00
level | 1
class | fix
component | multisite
edition | cme
The sorting order of the sites listed in the autocompleter of the "Site" filter
was wrong and mixed up with customer names.
Werk 16704 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# Fix discovery state filter
key | value
---------- | ---
compatible | yes
version | 2.3.0p3
date | 2024-05-13T08:00:06+00:00
level | 1
class | fix
component | multisite
edition | cre
The filter "Discovery state" used, e.g. in the "Unmonitored services" view, was
non-functional since version 2.0. No results were shown.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# Fix discovery state filter
key | value
---------- | ---
compatible | yes
- version | 2.3.0p2
? ^
+ version | 2.3.0p3
? ^
date | 2024-05-13T08:00:06+00:00
level | 1
class | fix
component | multisite
edition | cre
The filter "Discovery state" used, e.g. in the "Unmonitored services" view, was
non-functional since version 2.0. No results were shown.
+
[//]: # (werk v2)
# Fix discovery state filter
key | value
---------- | ---
compatible | yes
version | 2.3.0p2
date | 2024-05-13T08:00:06+00:00
level | 1
class | fix
component | multisite
edition | cre
The filter "Discovery state" used, e.g. in the "Unmonitored services" view, was
non-functional since version 2.0. No results were shown.