ID: 13702
Title: Agent controller: rename <tt>register-surrogate-pull</tt> to <tt>proxy-register</tt>
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This change is only incompatible for user who scripted tools against the
2.1.0b1 version of the agent controller <tt>cmk-agent-ctl</tt>.
The subcommand <tt>register-surrogate-pull</tt> has been renamed to
<tt>proxy-register</tt>, as it is easier to type and to remember.
ID: 13723
Title: Fix permission check when editing a report
Component: Reporting & Availability
Level: 2
Class: Security fix
Version: 2.2.0i1
When editing a report the permissions were not checked properly. A user could
guess the report name and owner and view the editing page of the report and
edit the report.
ID: 13772
Title: Add Google Cloud Platform support
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
Add support for Google Cloud Platform (GCP). To enable GCP monitoring add
an agent rule for "Google Cloud Platform (GCP)". For each project you want
to monitor you need a service account with the "Viewer" role and a json
private key. One rule has to be created per project.
Monitored GCP services
- Google Cloud Storage (GCS)
ID: 13344
Title: KUBE: kube_pod_status updated rule set
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
The status of a pod with an erronous container will often change. This happens even if there is
no meaningful change in the underlying problem. Previously, the kube_pod_status check would alert
if a specific status would persist for too long. However, changes of status would reset the
corresponding timer. The new rule set allows configuring a timer for a group of statuses.
ID: 13638
Title: REST API: Two-factor protected accounts may not access API
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
The REST API authentication was not handling the new two-factor authentication.
Since the authentication with the security key and one time tokens is not
usable with the API, we now completely block access to the REST API for those
user accounts.
If you have your personal account protected with the two-factor authentication
and want to use the REST API, you may create a dedicated (automation) account
for that.
ID: 13694
Title: Agent deployment: Don't try to activate incompatible units
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
On Linux systems where the agent controller <tt>cmk-agent-ctl</tt>
won't work (or is not even deployed), the systemd service unit
<tt>cmk-agent-ctl-daemon</tt> has been activated and would then fail.
The unit is not needed in that scenario, and is no longer deployed.
ID: 13695
Title: Adapt commandline interface of agent controller
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
This change only affects users who scripted the registration
command of the new agent controller <tt>cmk-agent-ctl register</tt>
using the first beta release.
The options of the command are now consistent with the options to
the similar updater command <tt>cmk-update-agent register</tt>.
ID: 13774
Title: Update list of available Infoblox services
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
Parsing of infoblox_services section would previously crash in case of "bfd" and
"outbound" services. "bfd" and "outbound" are now added to the list of service
IDs for infoblox devices.