ID: 7951
Title: check_mk: Don't crash upon missing hostname
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
The check_mk service no longer crashes if the host the linux agent is run on does not
provide the 'hostname' command.
ID: 7918
Title: nimble_latency: Do not crash and do not discover if required values are missing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
ID: 7978
Title: Service labels can now be discovered
Component: Core & setup
Level: 2
Class: New feature
Version: 1.7.0i1
The discovery functions of Checkmk checks can now produce a collection of
service labels together with the discovered services. This makes it possible
for the check developer to mark the services of the discovered services which
can then be grouped together in a flexible way.
The discovered service labels can be listed on the service discovery page of
WATO by enabling them with the button "Show discovered labels".
These labels are attributes of the discovered service and will be handled exactly
like them. They are discovered in one step and applied to the running
configuration in the same way. The cluster handling is also equal.
How make my checks produce service labels?
Instead of producing a two element tuple of <tt>(item, parameters)</tt> to
create a new service the discovery functions can now provide objects like this:
C+:
Service(
item="Interface 213",
parameters=None,
service_labels=ServiceLabels(
ServiceLabel(u"check_type", u"network_interface"),
ServiceLabel(u"interface_type", u"uplink"),
)
)
C-:
These objects can be returned / yielded like the tuples before. Both,
the parameters and the service_labels are optional arguments.
ID: 7921
Title: ucs_bladecenter_if: Use port ID if port name is missing
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously 'name' was always set and therefore wrong interface groups
were created.
ID: 7983
Title: Fix registering GUI commands with old multisite_commands
Component: Multisite
Level: 1
Class: Bug fix
Version: 1.7.0i1
The command registration API has changed with 1.6, but the 1.5 API
should still work as before for some time. This compatibility layer
has been fixed now.
ID: 8810
Title: systemd_services: Extension of services classification functionality
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.7.0i1
The systemd services summary check plugin obtains the functionality to assess static and activatingin a separate batch. Regarding the activating services, a new WATO rule has been implemented which allows to specify "lenient" time periods.
ID: 7917
Title: aws_costs_and_usage: Fixed missing service condition in related parameter set
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
This is an incompatible change which means that you have to adapted your rules.