Checkmk werks level1 June 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
272 discussions

[2.4.0] Checkmk Werk 15337 created: Add support for monitoring oracle 23ai

by Checkmk werks level 1

[//]: # (werk v2) # Add support for monitoring oracle 23ai key | value ---------- | --- date | 2024-06-18T12:37:00+00:00 version | 2.4.0b1 class | feature edition | cre component | checks level | 1 compatible | yes We extended the regular expression to detect processes of Oracle 23ai, we now also search for `db_pmon_`.

3 months

[2.4.0] Checkmk Werk 16767 created: NetApp via WebAPI: remove deprecated agent and plugin

by Checkmk werks level 1

[//]: # (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_)

3 months

[2.3.0] Checkmk Werk 16762 adapted: check certificates: fix signature algorithm configuration

by Checkmk werks level 1

Werk 16762 was adapted. The following is the new Werk, a diff is shown at the end of the message. [//]: # (werk v2) # check certificates: fix signature algorithm configuration key | value ---------- | --- date | 2024-04-24T06:54:32+00:00 version | 2.3.0b6 class | fix edition | cre component | checks level | 1 compatible | no Upgrading from 2.3.0b4 to a later version could cause the _Check Certificates_ settings for signature algorithms to load incorrectly due to missing choices in the old settings. This werk ensures correct loading. This work is incompatible because some old algorithms are no longer available. Old configurations are converted as follows: ## rsa - sha224: RSA_WITH_SHA224 - sha256: RSA_WITH_SHA256 - sha384: RSA_WITH_SHA384 - sha512: RSA_WITH_SHA512 - sha3_224: RSA_WITH_SHA224 - sha3_256: RSA_WITH_SHA256 - sha3_384: RSA_WITH_SHA384 - sha3_512: RSA_WITH_SHA512 ## ecdsa - sha224: ECDSA_WITH_SHA224 - sha256: ECDSA_WITH_SHA256 - sha384: ECDSA_WITH_SHA384 - sha512: ECDSA_WITH_SHA512 - sha3_224: ECDSA_WITH_SHA224 - sha3_256: ECDSA_WITH_SHA256 - sha3_384: ECDSA_WITH_SHA384 - sha3_512: ECDSA_WITH_SHA512 ## rsassa_pss Everything to RSASSA_PSS ## ed25519 ED25519 ## dsa - sha224: DSA_WITH_SHA224 - sha256: DSA_WITH_SHA256 - sha384: DSA_WITH_SHA256 - sha512: DSA_WITH_SHA256 - sha3_224: DSA_WITH_SHA224 - sha3_256: DSA_WITH_SHA256 - sha3_384: DSA_WITH_SHA256 - sha3_512: DSA_WITH_SHA256 ------------------------------------<diff>------------------------------------------- [//]: # (werk v2) # check certificates: fix signature algorithm configuration key | value ---------- | --- date | 2024-04-24T06:54:32+00:00 - version | 2.3.0 + version | 2.3.0b6 ? ++ class | fix edition | cre component | checks level | 1 compatible | no Upgrading from 2.3.0b4 to a later version could cause the _Check Certificates_ settings for signature algorithms to load incorrectly due to missing choices in the old settings. This werk ensures correct loading. This work is incompatible because some old algorithms are no longer available. Old configurations are converted as follows: ## rsa - sha224: RSA_WITH_SHA224 - sha256: RSA_WITH_SHA256 - sha384: RSA_WITH_SHA384 - sha512: RSA_WITH_SHA512 - sha3_224: RSA_WITH_SHA224 - sha3_256: RSA_WITH_SHA256 - sha3_384: RSA_WITH_SHA384 - sha3_512: RSA_WITH_SHA512 ## ecdsa - sha224: ECDSA_WITH_SHA224 - sha256: ECDSA_WITH_SHA256 - sha384: ECDSA_WITH_SHA384 - sha512: ECDSA_WITH_SHA512 - sha3_224: ECDSA_WITH_SHA224 - sha3_256: ECDSA_WITH_SHA256 - sha3_384: ECDSA_WITH_SHA384 - sha3_512: ECDSA_WITH_SHA512 ## rsassa_pss Everything to RSASSA_PSS ## ed25519 ED25519 ## dsa - sha224: DSA_WITH_SHA224 - sha256: DSA_WITH_SHA256 - sha384: DSA_WITH_SHA256 - sha512: DSA_WITH_SHA256 - sha3_224: DSA_WITH_SHA224 - sha3_256: DSA_WITH_SHA256 - sha3_384: DSA_WITH_SHA256 - sha3_512: DSA_WITH_SHA256

3 months

[2.3.0] Checkmk Werk 17029 created: Synthetic monitoring: Tests with status NOT RUN or SKIP go stale

by Checkmk werks level 1

[//]: # (werk v2) # Synthetic monitoring: Tests with status NOT RUN or SKIP go stale key | value ---------- | --- date | 2024-06-07T14:34:03+00:00 version | 2.3.0p7 class | fix edition | cee component | checks level | 1 compatible | no The test services become stale if the test status is NOT RUN, or SKIP. Previously, tests with any of these statuses would go to the WARN state. As a result of this werk, test services may change state and more the number of stale services may increase.

3 months

[2.3.0] Checkmk Werk 16798 created: ups_test: Handle unknown time since last test

by Checkmk werks level 1

[//]: # (werk v2) # ups_test: Handle unknown time since last test key | value ---------- | --- date | 2024-06-17T05:43:13+00:00 version | 2.3.0p7 class | fix edition | cre component | checks level | 1 compatible | yes The time since the last battery test is calculated via the difference between the current uptime and the uptime when the test was initiated. This means the time cannot be determined if the uptime of the test initiation is larger than the current uptime. Before, this lead to a ``` ValueError: Cannot render negative timespan ``` Now, the check will become UNKNOWN instead.

3 months

[2.4.0] Checkmk Werk 16798 created: ups_test: Handle unknown time since last test

by Checkmk werks level 1

[//]: # (werk v2) # ups_test: Handle unknown time since last test key | value ---------- | --- date | 2024-06-17T05:43:13+00:00 version | 2.4.0b1 class | fix edition | cre component | checks level | 1 compatible | yes The time since the last battery test is calculated via the difference between the current uptime and the uptime when the test was initiated. This means the time cannot be determined if the uptime of the test initiation is larger than the current uptime. Before, this lead to a ``` ValueError: Cannot render negative timespan ``` Now, the check will become UNKNOWN instead.

3 months

[2.4.0] Checkmk Werk 17029 created: Synthetic monitoring: Tests with status NOT RUN, SKIP or NOT SET go stale

by Checkmk werks level 1

[//]: # (werk v2) # Synthetic monitoring: Tests with status NOT RUN, SKIP or NOT SET go stale key | value ---------- | --- date | 2024-06-07T14:34:03+00:00 version | 2.4.0b1 class | fix edition | cee component | checks level | 1 compatible | no The test services become stale if the test status is NOT SET, NOT RUN, or SKIP. Previously, tests with any of these statuses would go to the WARN state. As a result of this werk, test services may change state and more the number of stale services may increase.

3 months

[2.2.0] Checkmk Werk 16821 created: mssql_datafiles: Fix computation of maximum size

by Checkmk werks level 1

Title: mssql_datafiles: Fix computation of maximum size Class: fix Compatible: compat Component: checks Date: 1718053672 Edition: cre Level: 1 Version: 2.2.0p28

3 months

[2.3.0] Checkmk Werk 17054 created: Test notifications: Match host and service level

by Checkmk werks level 1

[//]: # (werk v2) # Test notifications: Match host and service level key | value ---------- | --- date | 2024-06-17T09:54:41+00:00 version | 2.3.0p7 class | fix edition | cre component | notifications level | 1 compatible | yes Even if configured, host and service level did not match while testing notifications. This has been fixed.

3 months

[2.3.0] Checkmk Werk 16861 created: sql: Allow macros in 'Query or SQL statement' field

by Checkmk werks level 1

[//]: # (werk v2) # sql: Allow macros in 'Query or SQL statement' field key | value ---------- | --- date | 2024-06-13T15:56:27+00:00 version | 2.3.0p7 class | fix edition | cre component | checks level | 1 compatible | yes With the version 2.3, the usage of macros in the `Query or SQL statementw` field of the `Check SQL database` was disallowed. With this Werk, it's allowed again.

3 months

← Newer
1
...
9
10
11
12
13
14
15
...
28
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 June 2024