ID: 15437
Title: folder_config: deleting the root folder via the rest-api no longer causes an internal server error
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
This werk fixes an issue with the folder_config delete endpoint. Previously, when
attempting to delete the root folder via the rest-api, a 500 internal server error
would be raised. We now return a 401 with an appropriate error message.
ID: 15586
Title: host_tag: update multiple tag choices with rule dependency
Component: Setup
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, removing multiple tag choices with at least one tag choice
dependency in a rule caused a crash in both the user interface as well as
the REST API. This werk fixes this error.
ID: 15554
Title: user_config: allow all option for authorized_sites
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, the "all" value in authorized_sites was rejected due
to the validation mechanism. This werk fixes this issue. This fix does not
modify the default behaviour of authorized_sites when creating an user.
ID: 15551
Title: downtime: make the show downtimes endpoint more explicit
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
Prior to this werk, it was unclear under what circumstances the endpoint returned
service, host or both types of downtimes. In short, specifying the host_name parameter
limited the response to only return host downtimes. This werk introduces the downtime_type
parameter in order to make it easier to filter the results. This parameter is optional
as the same result can be achieved through the query parameter only.
Since the endpoint response is now more specific, user scripts must potentially be
adjusted accordingly:
* when the host_name parameter was previously specified, the user must now specify
the downtime_type parameter to "host" in order to receive the same downtimes as before
ID: 15436
Title: aux_tags: Deleting an aux tag now respects dependencies
Component: REST API
Level: 1
Class: Bug fix
Version: 2.3.0b1
This werk fixes an issue when deleting an aux tag that has a tag
group dependency. Previously, you could do this via the rest-api
but now it is not allowed. The response now includes a 409 status
code plus an appropriate message informing the client of the
problem. Client side scripts should be adjusted accordingly.
ID: 15541
Title: Replace BGP peer check plugin
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
The Arista BGP check plugin is replaced by a more general BGP peer check plugin.
The following new features are added:
<ul>
<li>Introduction of new SNMP sections cisco_bgp_peerv2 and cisco_bgp_peerv3
<li>Add description or VrfName if available which is available as check result and service label
<li>Add established time which is available as check result aswell as a metric
<li>Move less important check output to details
<li>Add configurable state mapping for admin state and peer state
</ul>
ID: 15577
Title: elasticsearch_nodes: Check plugin didn't consider ruleset
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
The parameter name in the WATO ruleset and in the check plugin were different.
Because of that the check plugin didn't consider the values from the ruleset.
This has now been fixed and the check plugin now considers the ruleset values.
ID: 15421
Title: Improve agent updater logging
Component: agents
Level: 1
Class: Bug fix
Version: 2.3.0b1
Previously, the agent updater reported many errors coming from the agent bakery with this unhelpful log output:
C+:
Unexpected answer from Checkmk server: Missing json data.
Maybe we are talking to an agent bakery from before Checkmk 2.0?
C-:
This happened for all errors that can not be interpreted by the agent bakery in a meaningful way.
Starting with this Werk, the agent updater will instead propagate the unknown error, e.g.:
C+:
Agent Bakery: Unhandled exception: KeyError: 'Signatures'
See ~/var/log/web.log on site 'mysite' for details.
C-:
As a last resort, if the agent updater still receives a response that it can't parse, it will still log
<tt>Unexpected answer from Checkmk server: Missing json data.</tt>,
but this time without the note about an old agent bakery, as this was not helpful at all.
<i>Bonus</i>:<br>
The error from the above example is now handled correctly:
C+:
Agent Bakery: Missing signatures in status response from central bakery. Maybe agents are unsigned?
C-:
ID: 15522
Title: Catalog of check plugins: show default parameters
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.3.0b1
In the <i>Catalog of check plugins</i> the default check parameters of each check plugin are now included.