[//]: # (werk v2)
# Fix checkmk errors appearing at the bottom of the page
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-05-28T16:05:26+00:00
level | 1
class | fix
component | wato
edition | cre
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.
Werk 16430 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# veeam_jobs: Always Monitor Result of Last Backup
key | value
---------- | ---
date | 2024-06-05T14:36:09+00:00
version | 2.4.0b1
class | fix
edition | cee
component | checks
level | 1
compatible | yes
Previously, the check plugin `veeam_jobs` would not always check the result of
the last backup job to determine the monitoring state. If the creation time was
an empty string, it would show `item not found`. Moreover, if the last
state of the plugin was `Starting`, `Working` or `Postprocessing`, then the
check would be OK, even if the last backup failed.
The check now shows all the information available unconditionally. Moreover,
* a Success result is OK,
* a Warning result is WARN,
* a Failed result is CRIT,
* a None result is OK or UNKNOWN. There is no change in behaviour in this case.
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# veeam_jobs: Always Monitor Result of Last Backup
key | value
---------- | ---
date | 2024-06-05T14:36:09+00:00
version | 2.4.0b1
class | fix
edition | cee
component | checks
level | 1
compatible | yes
Previously, the check plugin `veeam_jobs` would not always check the result of
the last backup job to determine the monitoring state. If the creation time was
an empty string, it would show `item not found`. Moreover, if the last
state of the plugin was `Starting`, `Working` or `Postprocessing`, then the
check would be OK, even if the last backup failed.
The check now shows all the information available unconditionally. Moreover,
+
* a Success result is OK,
* a Warning result is WARN,
* a Failed result is CRIT,
* a None result is OK or UNKNOWN. There is no change in behaviour in this case.
Title: BI configuration: "Toggle search preview"
Class: fix
Compatible: compat
Component: bi
Date: 1718110926
Edition: cre
Level: 1
Version: 2.2.0p28
The search preview for the BI nodes only worked if the entered data was changed again.
[//]: # (werk v2)
# Vertical graph axes: Always include zero for automatically adjusted ranges
key | value
---------- | ---
date | 2024-06-12T04:53:36+00:00
version | 2.3.0p7
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
As of this werk, the vertical axes of graphs with no explicitly specified vertical range will always
include zero. In case all the rendered data is non-negative, the vertical axis will start at zero.
Otherwise, the vertical axis will of course start below zero.
[//]: # (werk v2)
# BI configuration: "Toggle search preview"
key | value
---------- | ---
compatible | yes
version | 2.3.0p7
date | 2024-06-11T13:02:06+00:00
level | 1
class | fix
component | bi
edition | cre
The search preview for the BI nodes only worked if the entered data was changed again.
Werk 16767 was deleted. The following Werk is no longer relevant.
[//]: # (werk v2)
# NetApp via WebAPI: remove deprecated agent and plugin
key | value
---------- | ---
date | 2024-06-07T08:39:33+00:00
version | 2.4.0b1
class | feature
edition | cre
component | checks
level | 2
compatible | no
This werk impacts users who monitor a NetApp environment with the deprecated special agent "NetApp via WebAPI" (agent_netapp).
As of Checkmk version 2.4.0, the agent "NetApp via WebAPI" and its associated checks and inventory plugins have been removed.
Please configure the new special agent using the "NetApp via Ontap REST API" ruleset and perform a re-discovery.
The following plugins are no longer available:
- NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_aggr_)
- NetApp Ontap Filer: 7Mode Cluster Status (_netapp_api_cluster_)
- NetApp API Connection (_netapp_api_connection_)
- NetApp Filer: Cluster-Mode CPU Utilization (_netapp_api_cpu_)
- NetApp Clustermode Filer: NVRAM Battery (_netapp_api_cpu_nvram_bat_)
- NetApp Filer: 7Mode Global CPU Utilization (_netapp_api_cpu_utilization_)
- NetApp Filer: Disk (_Summarynetapp_api_disk_summary_)
- NetApp Filer Clustermode: PSU Fault Info (_netapp_api_environment_)
- NetApp Filer Clustermode: System Electrical Current (_netapp_api_environment_current_)
- NetApp Filer Clustermode: Fan Fault Info (_netapp_api_environment_fan_faults_)
- NetApp Filer Clustermode: System Fan Speed (_netapp_api_environment_fans_)
- NetApp Filer Clustermode: System Temperature (_netapp_api_environment_temperature_)
- NetApp Filer Clustermode: System Electrical Voltage (_netapp_api_environment_voltage_)
- NetApp Filer: FANs (_netapp_api_fan_)
- NetApp Filer: FANs Summary (_netapp_api_fan_summary_)
- NetApp Cluster-Mode: State of Fibrechannel Interfaces (_netapp_api_fcp_)
- NetApp Filer: State of Network Interfaces (_netapp_api_if_)
- NetApp Filer: Version Info (_netapp_api_info_)
- NetApp Filer: Used Space of LUNs (_netapp_api_luns_)
- NetApp Filer: Ports (_netapp_api_ports_)
- NetApp Filer 7Mode: Protocols (_netapp_api_protocol_)
- NetApp Filer: Power Supplies (_netapp_api_psu_)
- NetApp Filer: Power Supplies Summary (_netapp_api_psu_summary_)
- NetApp Filer: Used Space of qtrees in Volumes (_netapp_api_qtree_quota_)
- NetApp Filer: Used Space in Snapshots of Volumes (_netapp_api_snapshots_)
- NetApp Filer: Snapvault/Snapmirror Lag-time (_netapp_api_snapvault_)
- NetApp Filer: Overall System Health (_netapp_api_status_)
- NetApp Filer: Systemtime (_netapp_api_systemtime_)
- NetApp Filer: Temperature Sensors (_netapp_api_temp_)
- NetApp Filer 7Mode: vFiler CPU Utilization (_netapp_api_vf_stats_)
- NetApp Filer: vFiler Traffic (_netapp_api_vf_stats_traffic_)
- NetApp Filer: vFiler Status (_netapp_api_vf_status_)
- NetApp Filer: Used Space and Traffic of Volumes (_netapp_api_volumes_)
- NetApp Filer: vServer Status (_netapp_api_vs_status_)
- NetApp Filer: vServer Traffic Summary (_netapp_api_vs_traffic_)
[//]: # (werk v2)
# Vertical graph axes: Always include zero for automatically adjusted ranges
key | value
---------- | ---
date | 2024-06-12T04:53:36+00:00
version | 2.4.0b1
class | fix
edition | cre
component | multisite
level | 1
compatible | yes
As of this werk, the vertical axes of graphs with no explicitly specified vertical range will always
include zero. In case all the rendered data is non-negative, the vertical axis will start at zero.
Otherwise, the vertical axis will of course start below zero.
[//]: # (werk v2)
# BI configuration: "Toggle search preview"
key | value
---------- | ---
compatible | yes
version | 2.4.0b1
date | 2024-06-11T13:02:06+00:00
level | 1
class | fix
component | bi
edition | cre
The search preview for the BI nodes only worked if the entered data was changed again.