ID: 14133
Title: KUBE: Inventory: Move IP addresses from Software to Networking
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the networking information of a Kubernetes Node was found under Software > Applications
> Kubernetes > Network. With this werk, the information is in the path Networking > Kubernetes.
The old entries remain in the inventory history. This more consistent in how the information is
generally organized. Users which have included the path in their automation tools (including Checkmk
rules) need to change the path accordingly.
ID: 13259
Title: ups_out_load: valuespec transform from 2.0.0 representations was missing
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
After updating to Checkmk 2.1 rules configured for "output loads of UPSs and PDUs" check in
Checkmk 2.0 and below would result in unhandled exceptions "KeyError (levels)" and error messages
in the configuration interface "The type must be a dictionary, but it is a tuple."
This change introduces a transform function for values of "ups_out_load" turning them into
valid format.
ID: 13922
Title: UI dropdowns: Preserve given value on page load
Component: Multisite
Level: 1
Class: Bug fix
Version: 2.2.0i1
Upon initialization of autocompleter dropdowns, given values were sometimes unexpectedly erased and the dropdown left empty.
E.g. when editing a single metric dashlet or creating a forecast graph, given values for service description and metric name were sometimes removed upon loading the form. This is fixed to always show the given value of autocompleter dropdowns upon loading the respective page.
ID: 14370
Title: Add AWS/CloudFront check
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
This werk adds the AWS/CloudFront check.
With this check, you can monitor and add alarms on the following
metrics for each CloudFront distribution: Requests, Bytes downloaded,
Bytes uploaded, Total error rate, 4xx error rate, 5xx error rate.
A new service will be created for each CloudFront distribution and you
can filter the ones to monitor by distribution ID or by AWS tags.
ID: 14351
Title: Fix summary must be non empty crash when clustering services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Some services lead to a crash with the exception "summary must not be empty" on a cluster host.
This has been fixed. No user interaction required.
ID: 14343
Title: KUBE agent_kube: change ContainerTerminatedState's start and end time to be optional
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the Kubernetes special agent raised the error "[special_kube] TypeError: Can not convert
to timestamp: 'None' of type <class 'NoneType’>" when a terminated container had no information
about either its start or finish time. With this werk, the assumption that the start and finish
times are always set is removed, and is thus consistent with the Kubernetes specification.
The check plug-in is also modified to display the time-related information depending on what
fields are returned.
ID: 14053
Title: cisco_cpu_memory: Services with total memory of size 0 aren't discovered
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
CPU Memory utilization services with total memory of size 0 were previously
discovered and assumed the state UNKNOWN. Since the service delivered no
meaningful data in this case, it's no longer going to be discovered.
ID: 14345
Title: Storeonce4x agent handles token expiration
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
When executing the storeonce4x agent we now always request a new authentication token. This ensures we always have a valid token.
No user interaction required.
ID: 13684
Title: Agent Bakery: Minimize time locking the Checkmk configuration
Component: agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the agent bakery (or more precisely: The background job
scheduling a call to the agent bakery) locked the Checkmk configuration
for the entire baking time.
This caused some other operations that need access to the configuration,
like sending notifications or changing global settings, to fail with the
following error message:
C+:
Couldn't lock the Checkmk configuration. Another
process is running that holds this lock. In order for you to be
able to perform the desired action, you have to wait until the
other process has finished. Please try again later.
C-:
Instead of querying the Checkmk configuration multiple times, the agent
bakery now gathers all needed configurations on startup while holding
a lock, and releases it prior to invoking the more time consuming
baking of agent packages.
ID: 14342
Title: agent_prometheus & prometheus_build_info: change to display version of main instance
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the agent returned an error if the build_info PromQL returned multiple entries. This
effectively prevented the user from using the agent for a Prometheus cluster setup. This werk removes
this limitation and adjusts the Prometheus Build Service accordingly. The customization is only visible
for Prometheus instances running below version 2.14 and the details can be found in the updated man page