Title: Add support for monitoring oracle 23ai
Class: feature
Compatible: compat
Component: checks
Date: 1718714220
Edition: cre
Level: 1
Version: 2.2.0p28
We extended the regular expression to detect processes of Oracle 23ai, we now
also search for <code>db_pmon_</code>.
[//]: # (werk v2)
# Show traceback if a crash occurs during special agents execution
key | value
---------- | ---
date | 2024-06-17T14:27:57+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Currently, in the event of a crash during the execution of a special agent,
the traceback is not displayed in the user interface
but is only saved in the crash report on disk.
With this werk, the traceback will also be shown in the user interface.
[//]: # (werk v2)
# mknotifyd: use site names in service description
key | value
---------- | ---
date | 2024-05-27T14:57:03+00:00
version | 2.3.0p7
class | fix
edition | cre
component | checks
level | 2
compatible | no
This update affects users monitoring the _OMD Notify Connection_ services, regardless of whether the connection is encrypted.
Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1.
To resolve this issue, we have updated the service naming.
Now, the names of the involved sites will be shown in the format: _OMD MySite Notification Spooler connection to MyRemoteSite_.
Impact:
- Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual.
- Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible
- To maintain service history, users can create a service description translation rule. This can be done in the configuration at: _Setup_ > _Agents_ > _Access to agents_ > _Translation of service descriptions_. Use a regex or static string to map the old service names to the new ones.
[//]: # (werk v2)
# Add support for monitoring oracle 23ai
key | value
---------- | ---
date | 2024-06-18T12:37:00+00:00
version | 2.3.0p7
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_`.
[//]: # (werk v2)
# Show traceback if a crash occurs during special agents execution
key | value
---------- | ---
date | 2024-06-17T14:27:57+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Currently, in the event of a crash during the execution of a special agent,
the traceback is not displayed in the user interface
but is only saved in the crash report on disk.
With this werk, the traceback will also be shown in the user interface.
[//]: # (werk v2)
# mknotifyd: use site names in service description
key | value
---------- | ---
date | 2024-05-27T14:57:03+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 2
compatible | no
This update affects users monitoring the _OMD Notify Connection_ services, regardless of whether the connection is encrypted.
Previously it was not possible to correctly monitor the Notification Spooler connection with TLS. For encrypted incoming connections, the IP address and port were unavailable because managed by stunnel using Unix sockets. Consequently, services for encrypted connections were named incorrectly and always displayed the IP address as 127.0.0.1.
To resolve this issue, we have updated the service naming.
Now, the names of the involved sites will be shown in the format: _OMD MySite Notification Spooler connection to MyRemoteSite_.
Impact:
- Currently monitored services (e.g., those configured with unencrypted connections) will continue to work as usual.
- Upon rediscovery, new services will be discovered and will adopt the new naming convention. For this reason, this werk is flagged as incompatible
- To maintain service history, users can create a service description translation rule. This can be done in the configuration at: _Setup_ > _Agents_ > _Access to agents_ > _Translation of service descriptions_. Use a regex or static string to map the old service names to the new ones.
[//]: # (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_`.
[//]: # (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 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
[//]: # (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.