[//]: # (werk v2)
# jenkins: Remove character limitation in special agent configuration
key | value
---------- | ---
date | 2024-07-24T15:09:54+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Previously the "Jenkins instance to query" and "Username" fields were limited to 32 characters.
This limitation has been removed.
Werk 16846 was adapted. The following is the new Werk, a diff is shown at the end of the message.
[//]: # (werk v2)
# The custom instances of the MS SQL Server plugin are configured correctly
key | value
---------- | ---
date | 2024-07-19T11:09:57+00:00
version | 2.3.0p12
class | fix
edition | cee
component | checks
level | 2
compatible | yes
Previously, configuring custom instances, WATO used wrong key names:
`conn` instead of a correct `connection` and `auth` instead of
a correct `authentication`.
With this release the problem has been eliminated,
If you are using custom instances you need to bake and deploy new
agent package
------------------------------------<diff>-------------------------------------------
[//]: # (werk v2)
# The custom instances of the MS SQL Server plugin are configured correctly
key | value
---------- | ---
date | 2024-07-19T11:09:57+00:00
- version | 2.3.0p11
? ^
+ version | 2.3.0p12
? ^
class | fix
edition | cee
component | checks
level | 2
compatible | yes
Previously, configuring custom instances, WATO used wrong key names:
`conn` instead of a correct `connection` and `auth` instead of
a correct `authentication`.
With this release the problem has been eliminated,
If you are using custom instances you need to bake and deploy new
agent package
[//]: # (werk v2)
# agent_netapp_ontap: fix SSL certificate verification
key | value
---------- | ---
date | 2024-07-10T14:47:31+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This werk impacts who monitors Netapp Filers.
Previously, the connection to the Netapp endpoint
was only possible by excluding the SSL certificate check.
This was because the agent used the endpoint's IP address instead of its hostname,
preventing certificate verification.
Now the agent validates the certificate by comparing the common name with the host name as known to Checkmk.
Title: Microsoft Azure: Agent Info - adjust default levels for remaining reads
Class: fix
Compatible: compat
Component: checks
Date: 1721745177
Edition: cre
Level: 1
Version: 2.2.0p32
Since Microsoft is changing the way the API requests are rate limited,
the previous default levels for the remaining API reads where way to
high.
[//]: # (werk v2)
# Fix TCP access list handling for the event console
key | value
---------- | ---
date | 2024-07-24T10:16:32+00:00
version | 2.3.0p12
class | fix
edition | cre
component | ec
level | 1
compatible | yes
Due to a regression introduced in Checkmk 2.3, the TCP access list for the
event console was not working as intended. This has been fixed.
[//]: # (werk v2)
# agent_prism: fix SSL certificate verification
key | value
---------- | ---
date | 2024-07-10T13:55:32+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This werk impacts who monitors Nutanix Prism Clusters.
Previously, the connection to the Nutanix Prism endpoint
was only possible by excluding the SSL certificate check.
This was because the agent used the endpoint's IP address instead of its hostname,
preventing certificate verification.
Now the agent validates the certificate by comparing the common name with the host name as known to Checkmk.
[//]: # (werk v2)
# agent_netapp_ontap: Fails gracefully on an unauthorised request
key | value
---------- | ---
date | 2024-06-26T08:21:57+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This change is relevant if you are monitoring a NetApp filer
with the NetApp via ONTAP api check plugin.
Unauthorised requests caused the special agent to crash.
This werk improves this behaviour by only reporting a meaningful message in this case.
[//]: # (werk v2)
# Microsoft Azure: Agent Info - adjust default levels for remaining reads
key | value
---------- | ---
date | 2024-07-23T14:32:57+00:00
version | 2.3.0p12
class | fix
edition | cre
component | checks
level | 1
compatible | yes
Since Microsoft is changing the way the API requests are rate limited,
the previous default levels for the remaining API reads where way to
high.
[//]: # (werk v2)
# agent_prism: fix SSL certificate verification
key | value
---------- | ---
date | 2024-07-10T13:55:32+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This werk impacts who monitors Nutanix Prism Clusters.
Previously, the connection to the Nutanix Prism endpoint
was only possible by excluding the SSL certificate check.
This was because the agent used the endpoint's IP address instead of its hostname,
preventing certificate verification.
Now the agent validates the certificate by comparing the common name with the host name as known to Checkmk.
[//]: # (werk v2)
# agent_netapp_ontap: Fails gracefully on an unauthorised request
key | value
---------- | ---
date | 2024-06-26T08:21:57+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
This change is relevant if you are monitoring a NetApp filer
with the NetApp via ONTAP api check plugin.
Unauthorised requests caused the special agent to crash.
This werk improves this behaviour by only reporting a meaningful message in this case.