ID: 15252
Title: Fixed "processing of perfdata" condition
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
The logic for the processing of performance data was broken: It should only
be done when the global switch is activated <em>and</em> the processing is
enabled for the host/service in question. The condition was incorrectly
using an "or" for this, this has been fixed.
ID: 14581
Title: AWS: Allow configurable piggyback names
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
When creating a piggyback host for an EC2 instance, <tt>agent_aws</tt> uses the format
C+:
{Private IPv4 address}-{region}-{Instance ID}
C-:
This format guarantees that the piggback name is always unique, even when instances are restarted
and could potentially switch their IP address. However, in practice this problem can be neglected
and only using the Private IP DNS name as a piggyback name is safe. With this werk, the option
<tt>Piggyback names</tt> in the rule <tt>Amazon Web Services (AWS)</tt> allows you to configure how
piggyback hosts are named.
Note, that if a host changes it's name, then all historical data is lost.
ID: 15019
Title: Fix proxmox agent crash with shutdown nodes
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.2.0i1
The proxmox agent would fail with a KeyError when a proxmox VE node was shutdown.
The error occured because a we do not get information for the timezone of shutdown
nodes. The timezone information is used to convert timestamps for backups to utc.
When no timezone information is found for a node we use the timezone of the first
node we process.
ID: 14580
Title: DCD: Piggyback hosts are now updated and deleted again
Component: Dynamic host configuration
Level: 2
Class: Bug fix
Version: 2.2.0i1
The rule <tt>Dynamic host management</tt> allows user to configure automatic creation, updating and
deleting of hosts. With werk 15206 (included in 2.1.0p20), the underlying mechanism, <tt>Dynamic
Configuration Daemon</tt> would no longer update and delete hosts.
ID: 15215
Title: user_config: Error when creating a user with an idle timeout duration via the rest-api
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
This werk fixes an issue when creating a user via the REST-API
with an idle_timeout duration that was causing a 500 internal
server error.
ID: 15213
Title: rest_api: time_period exception/active time_ranges default
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
When creating a time_period via the REST-API, the exception time_ranges
field is not required, however if it's not provided, it will raise a
key error. This werk adds an empty list as a default value, which
aligns with the interface functionality of allowing an empty time_range
value. The second fix is the same issue but for the active time_ranges
field.
ID: 15212
Title: host_tag_groups: allow nullable on tag group choice ident
Component: REST API
Level: 1
Class: Bug fix
Version: 2.2.0i1
On creating a Tag Group, the tag group choice ident field can be null.
Response schema updated to reflect this. Also, HostTagGroup ident
field should be required. This field has also been updated.
ID: 15158
Title: Restart periodic notifications after FLAPPINGSTOP
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.2.0i1
In some cases, periodic notifications would still be halted
after FLAPPINGSTOP.
ID: 15091
Title: check_mk_agent: Add option "--force-inventory" in order to collect the output of the mk_inventory agent plugin
Component: agents
Level: 1
Class: New feature
Version: 2.2.0i1
Sometimes the full agent output, ie. the output of the agent itself and of all
installed agent plugins, of a host is needed for debugging or simulation
purposes.
Especially collecting the output of the agent plugin {{mk_inventory}} is not
very user-friendly because the execution depends on a special flag file. A user
has to delete or modified this flag file in order to get the output.
In general this intervention is not a good idea because it steps in the Checkmk
operations.
With the new option "--force-inventory" the output of {{mk_inventory}} is
collected and the Checkmk operations are not bothered anymore.
Example:
check_mk_agent --force-inventory > host.out
ID: 15143
Title: azure_load_balancer: Inventory for Azure Load Balancer added
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
A HW/SW inventory plugin has been added for Azure Load Balancer.
It shows the information about inbound NAT and outbound rules of
a load balancer.