ID: 13996
Title: Remove unresolved macros for additional IPs
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In case you're using the active check_icmp and ping all IP addresses, you may see the following issue:
<tt>(3, u'check_icmp: Failed to resolve $: Name or service not known')</tt>
This is caused by the fact the a host hasn't set additional IP addresses.
ID: 13938
Title: Requesting a non existing BI aggregation now results in a proper 404 response
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
Instead of an internal server error (status code 500),
requesting a non existing BI aggregation now results in a proper not found response (status code 404).
ID: 13801
Title: KUBE: Update inventory paths
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The HW/SW inventory entries Name and Namespace have been moved to the General path for all
Kubernetes hosts. An additional entry Object has been added which shows the Kubernetes object type.
ID: 13847
Title: local: Do not crash upon invalid metric names
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In Checkmk 1.6 and earlier the backend would silently sanitize metric names according to the nagios specification.
As this is no longer done, the local check plugin crashed upon invalid metric names.
As the metric names may be provided by third party components we no longer crash, but issue a warning instead.
The measured value will still be shown, and provided levels will be applied.
ID: 13799
Title: KUBE: add data processing information to Cluster Collector
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Previously, the Cluster collector service did not report any data processing
messages. This werk fixes this and displays the messages if they are available.
The issue was caused by an incorrect section header.
ID: 13646
Title: Fix host API calls in case a previous discovery failed
Component: REST API
Level: 1
Class: Bug fix
Version: 2.1.0b6
REST API calls returning host data structures could fail in case a bulk
discovery failed for one of the handled hosts before. The API calls failed
with a HTTP 500 error and a message like "Server was about to send an
invalid response: inventory_failed - Unknown field"
ID: 13937
Title: contact/service/host group responses now contain links to entries
Component: REST API
Level: 1
Class: New feature
Version: 2.2.0i1
Before, the REST API would only return the title of the objects in calls to the get all endpoints.
Now it will return a full link style data set.
ID: 13825
Title: Fix salesforce special agent
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The salesforce special agent arguments have not been comma separated.
ID: 13846
Title: Agent encryption: Enforce TLS for registered hosts
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
In general we may accept unencryptet agent data, as there are various reasons why a hosts agent might not be registered with the site.
However, once a host is registered the site <b>must</b> insist on a TLS encrypted connection.