Title: mk_redis: Fix for Werk #16329
Class: fix
Compatible: compat
Component: checks
Date: 1708512017
Edition: cre
Level: 1
Version: 2.2.0p23
With werk #16329 when a password was set, the plugin did not work.
This has now been fixed and configuring a password shouldn't cause any issues.
Title: netapp_ontap_snapvault: improves lagtime calculation
Class: fix
Compatible: compat
Component: checks
Date: 1708076378
Edition: cre
Level: 1
Version: 2.2.0p23
With this new type of calculation, since we don't have a reference for when this lagtime started or ended,
we always consider a month to be made up of 30 days.
[//]: # (werk v2)
# apidocs: improve the request/response examples
key | value
---------- | ---
date | 2024-02-21T11:07:55+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Previously the requests and urllib examples were hard coded to show
the same response samples and the same response status codes in
the request samples.
This werk addresses this issue by showing the correct possible
status codes for each endpoint.
[//]: # (werk v2)
# time_periods: Fix error when using time ranges shorter than a minute
key | value
---------- | ---
date | 2024-02-22T10:48:51+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 1
compatible | yes
Prior to this Werk, when trying to create a time period with a time range
shorter than 1 minute, an error code 500 was returned due to a validation
error. This Werk solves that problem, and time periods shorter than 1 minute
are validated correctly, so the endpoint now accepts them.
[//]: # (werk v2)
# aws: Inventorization of EC2 and ELB tags as host labels
key | value
---------- | ---
date | 2024-02-21T11:56:07+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
There was a problem during service discovery which prevented Checkmk
from assigning the AWS EC2 and ELB tags delivered by the AWS agent to
their respective piggyback hosts. This werk fixes the discovery process
such that the data is parsed properly and custom tags from AWS will
now show up as host labels on the created piggyback hosts.
[//]: # (werk v2)
# Checkmk Linux agent: ignore \*.dpkg-tmp files in plugin folder
key | value
---------- | ---
date | 2024-02-20T21:25:44+00:00
version | 2.4.0b1
class | fix
edition | cre
component | checks
level | 1
compatible | yes
The Checkmk agents for Linux, Solaris, AIX, OpenWrt and FreeBSD now ignore \*.dpkg-tmp files in the plugins folder.
They previously executed them inadvertedly as plugins.
This mostly fails silently (or even succeedes), but sometimes it is reported by the "Check_MK Agent" service.
[//]: # (werk v2)
# Change API specification computation
key | value
---------- | ---
date | 2024-02-17T13:24:38+00:00
version | 2.4.0b1
class | fix
edition | cre
component | rest-api
level | 2
compatible | yes
The specification of the REST API defines the structure of the API. It is
computed automatically from the implementation in Checkmk.
Previously the specification was computed during runtime when something
requested access to the specification. This could be a user opening ReDoc or the
Swagger UI. The specification was then computed ad-hoc and cached in the memory of the
apache process. This caused several issues:
* After spawning a new apache, the specification needed to be recomputed for
every process. This caused a delay in the first request hitting an
apache process asking for it.
* It was held in memory by every process consuming a few MB.
* The invalidation of the cache and computation of new specification could not
be triggered manually.
With this change the specification is now stored in the site and made available
to all apache processes from there.
With the dedicated command `cmk-compute-api-spec` the computation can now be
triggered in specific situations automatically or manually for debugging.
The specification is now updated in these situations:
* post-create hook: Create the initial spec after a site has been created
* post rename action: Update the spec after a site has been copied, restored or renamed
* update-config action: Update the spec after the site has been updated