ID: 7446
Title: EMKA checks did not recognize devices with recent sysObjectID
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 1.7.0i1
EMKA devices changes their sysObjectId and thus were not recognized by our
snmp_scan. Now we scan for both sysObjectIds to recognize the devices.
ID: 7980
Title: Prevent deletion of contact groups while referenced in hosts or folders
Component: WATO
Level: 1
Class: Bug fix
Version: 1.7.0i1
Previously contact groups could be deleted while still being referenced in hosts
or folders which lead to some strange effects in the GUI. Besindes the existing
validations the contact group deletion feature is now preventing the deletion
of groups in case it is still in use by a folder or host.
ID: 7938
Title: Unify status table columns in NEB and CMC.
Component: Livestatus
Level: 1
Class: New feature
Version: 1.7.0i1
<ul>
<li>Added <tt>average_latency_cmk</tt> and <tt>average_latency_real_time</tt>
columns, always containing zero.</li>
<li>Added <tt>average_latency_generic</tt> column, containing the average
latency of all active host/service checks.</li>
<li>Added <tt>core_pid</tt> column as an alias for <tt>nagios_pid</tt>.</li>
<li>Added <tt>has_event_handlers</tt> column.</li>
<li>Added <tt>helper_usage_generic</tt>, <tt>helper_usage_cmk</tt>, and
<tt>helper_usage_real_time</tt> columns, always containing zero.</li>
<li>Added <tt>livestatus_overflows</tt> and <tt>livestatus_overflows_rate</tt>
columns. The NEB queues accepted connections, so we never have overflows here.
Nevertheless, we provide these columns for consistency with CMC, and they always
contain zero.</li>
<li>Added <tt>livestatus_usage</tt> column.</li>
<li>Added <tt>num_queued_alerts</tt> column, always containing zero.</li>
<li>Added <tt>num_queued_notifications</tt> column, always containing zero.</li>
<li>Removed <tt>livecheck_overflows</tt> and <tt>livecheck_overflows_rate</tt>
columns from both NEB and CMC. They were unused for more than 6 years, they
never really worked well, and simply contain zero for ages. To reduce confusion,
those columns are gone now.</li>
</ul>
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.