ID: 8880
Title: Fix SNMP management board credentials
Component: Core & setup
Level: 2
Class: Bug fix
Version: 1.7.0i1
Monitoring of SNMP management boards did not work in the previous
1.6.0 releases when the management board credentials were different
from the host SNMP credentials.
ID: 7943
Title: Fixed graph zooming via mouse wheel.
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
The 1.6.0 branch contained a regression which broke the synchronized zooming
of graphs, you could even see JavaScript exceptions in the browser console
while zooming. This has been fixed.
ID: 7942
Title: Fixed dashlet refresh.
Component: Multisite
Level: 2
Class: Bug fix
Version: 1.7.0i1
Various dashlets didn't refresh automatically after they have been
rendered initially, e.g. the globes for host/service statistics.
This was a regression in the 1.6.0 branch and has been fixed now.
ID: 7755
Title: Jenkins: New special agent to query jenkins instances
Component: Checks & agents
Level: 2
Class: New feature
Version: 1.6.0b4
Special agent to monitor job and build states of a jenkins instance. Beside
the state of the job it gives informations about the job score and the time
since the last successful build. It also outputs informations about the last
build, like the time the build was triggered, the build id, duration and
result.
For performance reasons, the number of recognized jobs is limited to three
nested folder levels.
ID: 8858
Title: Fix broken distributed setup when Livestatus TLS is not enabled (1.6.0b5 regression, #7987)
Component: Site Management
Level: 2
Class: Bug fix
Version: 1.7.0i1
Werk #7987 broke distributed setups via Livestatus when Livestatus TLS is not enabled.
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: 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: 8783
Title: bulk notifications did not produce failed notifications
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.7.0i1
If a notification script returned a non-zero exit code and was
configured for bulk notifications no failed notifications were
shown in the GUI. With this fix one failed notification will
be produced for every notification present in the failed bulk.
Furthermore the view "Host and Service notifications" now shows
a "Final notification result" for every notification in a bulk.
ID: 7986
Title: Service labels can be used as rule conditions
Component: Core & setup
Level: 2
Class: New feature
Version: 1.7.0i1
The service labels, that are introduced with Checkmk 1.6 can now be used as
conditions in service rulesets (Host & Service Parameters). These conditions
can be configured like the host labels.
The labels can not be used in the rulesets "Service labels", because that
could result in a hen egg problem.
ID: 8784
Title: bulk notifications were sent multiple times
Component: Notifications
Level: 2
Class: Bug fix
Version: 1.7.0i1
Werk #8783 introduced a bug where bulk notifications
were not cleaned up and sent multiple times. All
notification scripts that produce no plugin output
like e.g. asciimail are affected.