Checkmk werks level2 August 2019

checkmk-werks-lvl2@lists.checkmk.com

6 participants
11 discussions

Checkmk Werk 7943: Fixed graph zooming via mouse wheel.

by Sven Panne

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.

5 years

Checkmk Werk 7942: Fixed dashlet refresh.

by Sven Panne

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.

5 years

Checkmk Werk 7755: Jenkins: New special agent to query jenkins instances

by Ronny Bruska

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.

5 years

Checkmk Werk 8858: Fix broken distributed setup when Livestatus TLS is not enabled (1.6.0b5 regression, #7987)

by Lars Michelsen

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.

5 years

Checkmk Werk 7978: Service labels can now be discovered

by Lars Michelsen

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.

5 years, 1 month

Checkmk Werk 8810: systemd_services: Extension of services classification functionality

by Wontek Hong

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.

5 years, 1 month

Checkmk Werk 8783: bulk notifications did not produce failed notifications

by Tom Baerwinkel

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.

5 years, 1 month

Checkmk Werk 7986: Service labels can be used as rule conditions

by Lars Michelsen

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.

5 years, 1 month

Checkmk Werk 8784: bulk notifications were sent multiple times

by Tom Baerwinkel

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.

5 years, 1 month

Checkmk Werk 7717: Windows Agent 1.6 Beta 4: new features

by Sergey Kipnis

ID: 7717 Title: Windows Agent 1.6 Beta 4: new features Component: Checks & agents Level: 2 Class: New feature Version: 1.6.0b4 Summary of the features introduced in Windows Agent beta 4: - Asynchronous plugins with 'cache_age' set to 0 are supported now. In previous version such plugins have been assumed as synchronous. - The Uninstallation of the Windows Agent doesn't remove 'config' and 'state' directories from the Agent Data directory to prevent user data loss. - The start of the Windows Agent may be delayed by a few seconds to allow asynchronous plugins to finish their work. This feature has no effect for normal situation when agent is running as a service, but may be useful to test asyncronous plugins. - Now the Agent uses next directories: The Windows Agent installs own binary files in the directory "Program Files (x86)\checkmk\service" For user and bakery data the Windows Agent uses the directory "ProgramData\checkmk\agent" - The macroses used in the configuration files had been renamed $BUILTIN_AGENT_PATH$ -> is C:/Program Files(x86)/checkmk/service/ $BUILTIN_PLUGINS_PATH$ -> is C:/Program Files(x86)/checkmk/service/plugins $CUSTOM_AGENT_PATH$ -> is C:/ProgramData/checkmk/agent/ $CUSTOM_PLUGINS_PATH$ -> is C:/ProgramData/checkmk/agent/plugins $CUSTOM_LOCAL_PATH$ -> is C:/ProgramData/checkmk/agent/local - The logfile check_mk.log have been moved to the "ProgramData/checkmk/agent/log" directory - The configuration files check_mk.user.yml and check_mk.yml had been revised, cleaned of old and unused data and better documented. - The default timeout for all plugins is set to 60 seconds, previously the timeout was set to 30. - Now all names in any yml configuration file with the leading underscore are considered invalid and skipped from the output when the command showconfig is used.

5 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 August 2019