ID: 15385
Title: agent_kube: ignore resource quota with no hard resource requirement
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, the Kubernetes special agent failed when the Kubernetes API reported
a resource quota but with no underlying hard resource requirement for either memory
or cpu. This werk fixes this issue.
ID: 15376
Title: dcd: Fixes 2 issues with phases 1.1 & 2.4 calling incorrectly formed urls.
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
This werk fixes 2 issues with the dcd that were introduced after making
the rest api url matching stricter.
The first issue was with the Phase 2.4 Activate Changes failing, This was
because of incorrectly formed redirect urls. The urls are now fixed.
The second issue was with a distributed monitoring setup and with
Phase 1.1 Executing on site... being called, again, with an incorrect
url. The url has now been fixed here too.
ID: 15416
Title: Agent receiver is accessible via IPv4 and IPv6
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The agent receiver listens on port 8000 (per default) on the Checkmk server.
It handles all calls from the agent controller, e.g., agent registration.
While it previously only listened on IPv4 networks, it's now accessible via IPv4 and IPv6.
ID: 15383
Title: folder_config: adapt folder name pattern of get, put, delete endpoints to post endpoint
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, the folder name pattern for the get, update and delete endpoints was too restrictive
with respect to the create endpoint. This werk fixes this.
ID: 15406
Title: Renaming of hosts: Handle TLS agent registrations correctly
Component: setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
When renaming hosts which were registered for TLS-encrypted agent communication, Checkmk ran into
the following error:
C+:
TypeError: '<' not supported between instances of 'tuple' and 'str'
C-:
Furthermore, in distributed setups, renaming TLS-registered hosts which were monitored on remote
sites lead to a loss of registration, which prevented any further agent communication until the
affected hosts were re-registered.
ID: 15147
Title: azure_virtual_machine: New checks added
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
Monitoring of Azure VM is extended with five new checks.
The new monitored checks are:
LI: Microsoft Azure Virtual Machines: CPU Utilization
LI: Microsoft Azure Virtual Machines: Burst CPU Credits
LI: Microsoft Azure Virtual Machines: Memory
LI: Microsoft Azure Virtual Machines: Disk
LI: Microsoft Azure Virtual Machines: Network IO
The new services will be automatically discovered if you have
an Azure VM mapped to its own host in Checkmk.
ID: 13974
Title: Correct ruleset search documentation text
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
The documentation text of the "deprecated" filter option in the 'list rulesets' endpoint incorrectly stated that
it will include deprecated rules in the results.
Instead it only shows deprecated rules, no non-deprecated rules.
The documentation has been updated in order to reflect the current and correct behaviour.
ID: 13973
Title: Putting a service into downtime no longer requires access to the corresponding host in the REST API
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Putting a service into downtime using the REST API required permissions to access the corresponding host in the REST API.
The REST API call would fail with an error message stating that,
```
Host 'myhost' exists, but is not monitored. Activate the configuration?
```
This behaviour doesn't match the GUI's and is now no longer the case.