ID: 8845
Title: Web-API: Prevent adding wrong encoded labels to hosts / rulesets
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
In previous 1.6 releases the Web API did not validate the labels that
could e.g. be added to hosts strictly enough. When using "python" as
"request_format" this could result in a broken configuration, leading
to exceptions in several places of the GUI.
The Web API now ensures the received labes are all unicode strings as
Checkmk expects.
ID: 7719
Title: Windows Agent 1.6: The section 'ps' by default doesn't generate full paths in the output
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.6.0b5
ID: 8842
Title: Show host labels in "cmk -D HOST" output
Component: Core & setup
Level: 1
Class: New feature
Version: 1.6.0b5
The effective host labels can now be displayed on
the command line using "cmk -D HOST".
ID: 8840
Title: Docker: Introduce host labels for different docker hosts
Component: Core & setup
Level: 1
Class: New feature
Version: 1.6.0b5
Docker nodes will now automatically marked with the discovered label "cmk_docker_object:node".
The docker container host objects will be marked with the host label "cmk_docker_object:container".
ID: 8841
Title: Change internal mechanic of discovered host labels
Component: Core & setup
Level: 1
Class: New feature
Version: 1.6.0b5
The discovered host labels which were introduced during the first beta
versions of Checkmk 1.6 had to be reworked for some reasons. The new
implementation is now based on the Service discovery mechanism, which
makes several things a lot easier for us.
Host labels are now discovered during the procedure of Checkmk service
discovery. All discovery functions of the checks are able to either
discover services and host labels.
<ul>
<li>The "Check_MK Discovery" service tells you about new found host labels,
just like about services.</li>
<li>You can use the "Service discovery" page of WATO to view the discovered
host labels. New discovered host labels now trigger a warning state by default.
This state can be configured using the "Periodic service discovery" ruleset.
<li>The automatic activation function, that can be configured in the "Periodic
service discovery" ruleset may be used to automatically add new host labels on
a regular base.</li>
<li>Whenever you execute a service discovery (via command line, GUI or API),
the host labels will also be discovered.</li>
<li>CEE: The DCD can immediately add host labels when you have enabled the
service discovery for a DCD connection.</li>
</ul>
Check programmers: You may add something like this to your discovery
functions for creating host labels:
C+:
yield HostLabels(
HostLabel(u"os", u"Windows"),
HostLabel(u"type", u"security"),
)
C-:
This adds two host labels os:Windows and type:security to the host.
ID: 7864
Title: aws_glacier_limits and aws_glacier_summary: New checks to monitor AWS/Glacier limits and to overview over all AWS/Glacier vaults
Component: Checks & agents
Level: 1
Class: New feature
Version: 1.7.0i1
ID: 7865
Title: aws_agent and aws checks: Fixed exception with empty EC2 instance list and output of identical WARN/CRIT messages
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Fixed exception in AWS Agent when there are no EC2 instances but EC2 monitoring is enabled.
Fixed output of multiple identical WARN and CRIT messages if limits were reached.