Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15974 discussions

Check_MK Werk 5936: Fixed broken metrics in Fireeye statistics checks. Affected performance graphs are now generated correctly.

by Simon Betz

ID: 5936 Title: Fixed broken metrics in Fireeye statistics checks. Affected performance graphs are now generated correctly. Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i4

6 years, 6 months

Check_MK Werk 5943: Fixed broken PDF export of host/service history views

by Lars Michelsen

ID: 5943 Title: Fixed broken PDF export of host/service history views Component: Reporting & Availability Level: 1 Class: Bug fix Version: 1.5.0i4 This issue seemed to be introduced with 1.4.0p26.

6 years, 6 months

Check_MK Werk 5942: Fixed broken BI availability with limit set to 0 (regression in 1.4.0p26)

by Lars Michelsen

ID: 5942 Title: Fixed broken BI availability with limit set to 0 (regression in 1.4.0p26) Component: Multisite Level: 1 Class: Bug fix Version: 1.5.0i4 In case you are affected, you can set the availability limit to another value than 0 to workaround this issue.

6 years, 6 months

Check_MK Werk 5317: BI rules: Fixed renaming rule

by Simon Betz

ID: 5317 Title: BI rules: Fixed renaming rule Component: BI Level: 1 Class: Bug fix Version: 1.5.0i4

6 years, 6 months

Check_MK Werk 5797: netapp_api_luns: fixed interchanged free/used names in WATO configuration rule

by Andreas Boesl

ID: 5797 Title: netapp_api_luns: fixed interchanged free/used names in WATO configuration rule Component: WATO Level: 1 Class: Bug fix Version: 1.5.0i4 The levels configuration for netapp_api_luns was incorrectly named. The free space levels were treated as used space and vice versa.

6 years, 6 months

Check_MK Werk 5931: Fixed "skipping unimplemented check" warning message of active checks

by Simon Betz

ID: 5931 Title: Fixed "skipping unimplemented check" warning message of active checks Component: WATO Level: 1 Class: Bug fix Version: 1.5.0i4 If an active check was disabled via the rule "Disabled services" and then readmitted to the list of monitored services of the host on the service discovery page, this active check was falsely stored to the related autochecks file which caused above warning message.

6 years, 6 months

Check_MK Werk 5933: HW/SW inventory: Fixed AttributeError

by Simon Betz

ID: 5933 Title: HW/SW inventory: Fixed AttributeError Component: HW/SW Inventory Level: 1 Class: Bug fix Version: 1.5.0i4

6 years, 6 months

Check_MK Werk 5941: Fixed nagios using outdated config when not using "cmk -R/-O"

by Lars Michelsen

ID: 5941 Title: Fixed nagios using outdated config when not using "cmk -R/-O" Component: Other Components Level: 1 Class: Bug fix Version: 1.5.0i4 When using "omd start/restart" or the init script etc/init.d/nagios to start or restart nagios, it was possible that the core started with an outdated configuration. During start/restart the nagios init script is working in two steps: 1. config validation and 2. start/restart of the nagios process. During both steps the whole object configuration (etc/nagios/conf.d) needs to be processed. To optimize this the first step is perfoming some precompiling of the read config files. The result is saved in the file var/nagios/objects.precache and read by the core during startup instead of the single object config files. The init script had an option set (CORE_NOVERIFY=yes) in all cases that prevented the config verification even when executed manually. Without the config verification the object precache was not updated before the restart, making the core load an outdated file. The variable CORE_NOVERIFY=yes should only be set when the config verification has already been done. For example cmk -R/-O is doing exactly this. A workaround is to trigger the restarts using "cmk -R".

6 years, 6 months

Check_MK Werk 5940: Fixed broken packaging of CME in 1.5

by Lars Michelsen

ID: 5940 Title: Fixed broken packaging of CME in 1.5 Component: Other Components Level: 1 Class: Bug fix Version: 1.5.0i4 The error "Configuration Error: 'module' object has no attribute 'current_customer'" occured while creating the core configuration for sites created with 1.5.

6 years, 6 months

Check_MK Werk 5939: Alert handlers can now be packed into MKPs

by Lars Michelsen

ID: 5939 Title: Alert handlers can now be packed into MKPs Component: alerts Level: 1 Class: New feature Version: 1.5.0i4

6 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1