Werk 16856 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: disk_smb: Allow macros in 'NetBIOS name of the server' field
Class: fix
Compatible: compat
Component: checks
Date: 1716895280
Edition: cre
Level: 1
Version: 2.2.0p28
With the rework of disk_smb active check in version 2.1.0, using macros in
'NetBIOS name of the server' was disallowed. Now, the macros are enabled
for this field again.
------------------------------------<diff>-------------------------------------------
Title: disk_smb: Allow macros in 'NetBIOS name of the server' field
Class: fix
Compatible: compat
Component: checks
Date: 1716895280
Edition: cre
Level: 1
- Version: 2.2.0p27
? ^
+ Version: 2.2.0p28
? ^
With the rework of disk_smb active check in version 2.1.0, using macros in
'NetBIOS name of the server' was disallowed. Now, the macros are enabled
for this field again.
Werk 16856 was adapted. The following is the new Werk, a diff is shown at the end of the message.
Title: disk_smb: Allow macros in 'NetBIOS name of the server' field
Class: fix
Compatible: compat
Component: checks
Date: 1716895280
Edition: cre
Level: 1
Version: 2.2.0p27
With the rework of disk_smb active check in version 2.1.0, using macros in
'NetBIOS name of the server' was disallowed. Now, the macros are enabled
for this field again.
------------------------------------<diff>-------------------------------------------
Title: disk_smb: Allow macros in 'NetBIOS name of the server' field
Class: fix
Compatible: compat
Component: checks
Date: 1716895280
Edition: cre
Level: 1
- Version: 2.2.0p28
? ^
+ Version: 2.2.0p27
? ^
With the rework of disk_smb active check in version 2.1.0, using macros in
'NetBIOS name of the server' was disallowed. Now, the macros are enabled
for this field again.
Title: Fix checkmk errors appearing at the bottom of the page
Class: fix
Compatible: compat
Component: wato
Date: 1716912326
Edition: cre
Level: 1
Version: 2.2.0p27
A certain class of errors, including time out errors appeared at
the bottom of a page, making the error difficult to notice, especially
when viewing large tables. With this werk, these error messages
will appear on top of the page like all other errors.
Title: netapp: Fix crash when setting state in snapshot reserve service rule
Class: fix
Compatible: compat
Component: checks
Date: 1716914026
Edition: cre
Level: 1
Version: 2.2.0p27
A problem in the NetApp Snapshot Reserve rule caused a crash
when setting the "State when no reserve is configured" option.
This werk fixes the bug such that the state can be defined
as expected.
[//]: # (werk v2)
# netapp: Fix crash when setting state in snapshot reserve service rule
key | value
---------- | ---
compatible | yes
version | 2.3.0p5
date | 2024-05-28T16:33:46+00:00
level | 1
class | fix
component | checks
edition | cre
A problem in the NetApp Snapshot Reserve rule caused a crash
when setting the "State when no reserve is configured" option.
This werk fixes the bug such that the state can be defined
as expected.
[//]: # (werk v2)
# Predictive levels: Label upper levels correctly in service graphs
key | value
---------- | ---
date | 2024-05-22T21:58:01+00:00
version | 2.3.0p5
class | fix
edition | cee
component | metrics
level | 1
compatible | yes
When using predictive levels, the predicted thresholds are automatically added to the corresponding
service graphs. For metrics declared via the new API, upper levels were by mistake labeled as lower
levels.
[//]: # (werk v2)
# hyperv_vms: Mapping of VM-to-monitoring state causes UNKNOWN services
key | value
---------- | ---
date | 2024-05-27T14:11:42+00:00
version | 2.3.0p4
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This is a regression since Checkmk 2.3.0.
When configuring the rule _Microsoft Hyper-V Server VM state_ with option
_Translation of VM state to monitoring state: Direct mapping of VM state to monitoring state_,
the matching _VM_ services previously showed up with status _UNKNOWN_ for all VM states that were not
explicitly configured by the rule.
[//]: # (werk v2)
# Limit "Send out notification" on test to HTML and ASCII Email
key | value
---------- | ---
date | 2024-05-31T10:16:11+00:00
version | 2.3.0p5
class | fix
edition | cre
component | notifications
level | 1
compatible | yes
If you used the option "Send out notification according to notification rules
(uncheck to avoid spam)" in "Test configuration" for other notification methods
than "HTML Email" or "ASCII Email", the processed notification script could
crash with a Traceback.
This is caused by missing notification parameters that differ for each
notification method.
We now limit the mentioned option to HTML and ASCII Email, as originally
intended.
Testing all other notification methods is still possible, but you can only send
out HTML and ASCII notifications.