[//]: # (werk v2)
# Prevent "Internal server errors" when saving large forms
key | value
---------- | ---
date | 2024-05-21T13:43:42+00:00
version | 2.4.0b1
class | fix
edition | cre
component | wato
level | 1
compatible | yes
This werk fixes an issue when saving extra large forms. The
problem was that there was a limit on the size of the form
data, therefore, on reaching the size, would cause a crash.
This limit has now been removed, thus preventing crashes.
[//]: # (werk v2)
# Fix performance issues when processing performance data (process_perfdata.pl) and missing metric data
key | value
---------- | ---
date | 2024-05-22T13:57:02+00:00
version | 2.4.0b1
class | fix
edition | cre
component | omd
level | 3
compatible | yes
This werk affects all users of Checkmk Raw.
You might have perceived a severe performance degradation in Checkmk 2.3.0 and a lot of errors in
the NPCD log. This was due to missing RRD packages and thus expensive fall-back computations.
This werk fixes a performance issue in combination with potentially missing metric data, which can
result in gaps in the service graphs.
Title: Crash: liebert_maintenance: ValueError("Cannot render negative timespan") when time is overdue
Class: fix
Compatible: compat
Component: checks
Date: 1716279854
Edition: cre
Level: 1
Version: 2.2.0p27
<code>liebert_maintenance</code> check would crash with <code>ValueError("Cannot render negative timespan")</code> if the
value for "Next maintenance" is in the past.
This change now renders positive and negative values differently (also only printing days) adding
<code>'overdue'</code> if date for next maintenance is located in the past.
[//]: # (werk v2)
# Synthetic Monitoring: Only persist new HTML logs
key | value
---------- | ---
date | 2024-05-21T18:45:53+00:00
version | 2.4.0b1
class | fix
edition | cee
component | checks
level | 1
compatible | yes
Before this werk, the test services wrote their HTML logs to disk every time they were checked. As
of this werk, a log is only written to disk if it is newer than the currently stored version. This
saves disk I/O.
[//]: # (werk v2)
# Synthetic Monitoring: Remove 'cmk/rmk/html_last_error_log' service label
key | value
---------- | ---
date | 2024-05-21T18:38:26+00:00
version | 2.4.0b1
class | fix
edition | cee
component | checks
level | 1
compatible | yes
The service label mentioned above is not discovered anymore, since it was unused. Previously,
discovered test services always had this label.
[//]: # (werk v2)
# Crash: liebert_maintenance: ValueError("Cannot render negative timespan") when time is overdue
key | value
---------- | ---
date | 2024-05-21T08:24:14+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
`liebert_maintenance` check would crash with `ValueError("Cannot render negative timespan")` if the
value for "Next maintenance" is in the past.
This change now renders positive and negative values differently (also only printing days) adding
`'overdue'` if date for next maintenance is located in the past.
[//]: # (werk v2)
# check_mailboxes: fix issue with EWS distinguished folder
key | value
---------- | ---
date | 2024-05-15T07:47:43+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The active check "check_mailboxes" could fail with a `KeyError: 'folders'` when trying to retrieve an exchange mailbox's folders via the EWS protocol.
With this werk the used library `exchangelib` is updated to v5.4.0, which prevents the underlying issue in retrieving certain exchange folders.
Title: check_mailboxes: fix issue with EWS distinguished folder
Class: fix
Compatible: compat
Component: checks
Date: 1715759263
Edition: cre
Level: 1
Version: 2.2.0p27
The active check "check_mailboxes" could fail with a <code>KeyError: 'folders'</code> when trying to retrieve an exchange mailbox's folders via the EWS protocol.
With this werk the used library <code>exchangelib</code> is updated to v5.4.0, which prevents the underlying issue in retrieving certain exchange folders.
[//]: # (werk v2)
# Topology visualization: No longer crashes when trying to migrate legacy configuration to new format
key | value
---------- | ---
date | 2024-05-13T09:50:21+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
Title: seh_ports: support new OIDs from updated sehMIB v2.5
Class: feature
Compatible: compat
Component: checks
Date: 1715751377
Edition: cre
Level: 1
Version: 2.2.0p27
The <code>seh_ports</code> 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 <code>seh_ports</code> deal with the new format next to the old one.