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.
ID: 15142
Title: azure_resource_health: Monitor Azure Resource Health
Component: Checks & agents
Level: 1
Class: New feature
Version: 2.2.0i1
It's now possible to monitor the health of Azure resources.
A new resource health service will be added for every monitored
resource.
To monitor Azure resources and their health you have to configure
the related special agent Microsoft Azure.
ID: 15251
Title: Fixed "downtimes_with_extra_info" columns in host/service tables
Component: Livestatus
Level: 1
Class: Bug fix
Version: 2.2.0i1
The "is_pending" part of the "downtimes_with_extra_info" column in the
"hosts" and "services" table reported all downtimes to be pending. This has
been fixed and the information now reflects the real state of the downtime.
This affected only Livestatus for the Nagios core, the CMC part was correct.
ID: 14690
Title: Fixed "type" column in "downtimes" table
Component: Livestatus
Level: 1
Class: Bug fix
Version: 2.2.0i1
The "type" column in the Livestatus "downtimes" table incorrectly contained
information about the active/pending state of the downtime, now it is
providing information about its type (host or service downtime).
Note that for both kinds of information there is another, more appropriate
column ("is_pending" and "is_service").
ID: 14724
Title: Improve EC performance when processing large logwatch.ec spool files
Component: Event Console
Level: 1
Class: New feature
Version: 2.2.0i1
The performance and stability of the event console is now improved when
processing large logwatch.ec generated spool files.
logwatch.ec used to be able to generate spool files with unlimited size.
The size of the spool files is now limited to 1 MiB. In case this limit
is reached the multiple spool files are created.