Checkmk werks level1 May 2018

checkmk-werks-lvl1@lists.checkmk.com

6 participants
111 discussions

Check_MK Werk 6169: Discovery page: Fixed incompatibility with central 1.4 and remote 1.5 site

by Lars Michelsen

ID: 6169 Title: Discovery page: Fixed incompatibility with central 1.4 and remote 1.5 site Component: WATO Level: 1 Class: Bug fix Version: 1.6.0i1 An error "ValueError: could not convert string to float:" was shown when performing the service discovery on a host that is monitored by a 1.5 site while the central WATO site is a 1.4 site.

6 years, 3 months

Check_MK Werk 6154: Fixed different Check_MK calls (parent scan, baking, rrd conversion) in some cases

by Lars Michelsen

ID: 6154 Title: Fixed different Check_MK calls (parent scan, baking, rrd conversion) in some cases Component: Core & setup Level: 2 Class: Bug fix Version: 1.6.0i1 When using some check specific configuration variables (like e.g. fileinfo_groups), the mentioned Check_MK calls could not be used. An error like this was shown: Cannot read in configuration file /omd/sites/beta/etc/check_mk/conf.d/wato/rules.mk: name 'fileinfo_groups' is not defined

6 years, 3 months

Check_MK Werk 6153: Fixed broken notifications and alert handling (Regression in 1.5.0b5)

by Lars Michelsen

ID: 6153 Title: Fixed broken notifications and alert handling (Regression in 1.5.0b5) Component: Notifications Level: 2 Class: Bug fix Version: 1.6.0i1 The notifications and alert handling were not working correctly at all. Better use the 1.5.0b5 only in test environments where you don't need these features.

6 years, 3 months

Check_MK Werk 6155: Service discovery page: Active checks were not correctly shown in specific cases

by Lars Michelsen

ID: 6155 Title: Service discovery page: Active checks were not correctly shown in specific cases Component: WATO Level: 1 Class: Bug fix Version: 1.6.0i1 It could happen that some active checks were not correctly shown in the tables "active checks" or "disabled active checks". This was caused by specific disabled services rules. For example when using this two rules: 1. Enable all services starting with "HTTP" 2. Disable all services In this situation the HTTP service was not displayed on the discovery page.

6 years, 3 months

Check_MK Werk 6152: Notification conditions can now be displayed in notification rule table

by Lars Michelsen

ID: 6152 Title: Notification conditions can now be displayed in notification rule table Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 The last column can now expand the number of conditions to the list of match conditions of the rule.

6 years, 3 months

Check_MK Werk 6151: Net-SNMP: Add some patch trying to fix SNMPv3 communication in some cases

by Lars Michelsen

ID: 6151 Title: Net-SNMP: Add some patch trying to fix SNMPv3 communication in some cases Component: Other Components Level: 1 Class: Bug fix Version: 1.6.0i1 When using SNMPv3 communication issues with some devices may occur. From the user point of view timeouts are reported by Check_MK originating from Net-SNMP not receiving a valid response. This kind of issue is related to a broken negotiation (related to the maximum message size) between the monitoring and the monitored device.

6 years, 3 months

Check_MK Werk 6111: heartbeat_crm: return CRIT if the connection to the cluster fails

by Tom Baerwinkel

ID: 6111 Title: heartbeat_crm: return CRIT if the connection to the cluster fails Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1

6 years, 3 months

Check_MK Werk 6150: docker_container_status: Fix crash when receiving data from multiple hosts

by Lars Michelsen

ID: 6150 Title: docker_container_status: Fix crash when receiving data from multiple hosts Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1

6 years, 3 months

Check_MK Werk 6149: ps: The linux ps check CPU utilization calculation changed since 1.4.0p27

by Lars Michelsen

ID: 6149 Title: ps: The linux ps check CPU utilization calculation changed since 1.4.0p27 Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 The calculation of the CPU utilization of processes on linux systems was not taking the number of CPU cores into account for a long time. This results in CPU utilizations reported with more than 100%, up to 100%*CPU-cores. For example in case 3 processes use 3 of 6 cores at 100%, this resulted in a usage of 300%. The intention of the change in 1.4.0p27 was to make the windows and linux ps checks both take the number of CPU cores into account and cap the usage at 100%. The problem with this change is that all possibly existing thresholds that have been configured for the old scheme will not work anymore with the new scheme. We have now reverted the changes version 1.4.0p27 introduced to get the old behavior back. In a future release, we will finally make the switch to the new scheme. But this will be done in a compatible way where the already configured thresholds will still work.

6 years, 3 months

Check_MK Werk 6081: Fixed info extension by node name of cluster-aware checks if host if not part of a cluster

by Simon Betz

ID: 6081 Title: Fixed info extension by node name of cluster-aware checks if host if not part of a cluster Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1

6 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2018