Checkmk werks level1 March 2019

checkmk-werks-lvl1@lists.checkmk.com

13 participants
108 discussions

Check_MK Werk 7241: Fixed uploading customer logo

by Lars Michelsen

ID: 7241 Title: Fixed uploading customer logo Component: WATO Level: 1 Class: Bug fix Version: 1.6.0i1 Fixed uploading customer logos for some customers. An error like this could occur: "KeyError ('globals')"

5 years, 6 months

Check_MK Werk 7127: msexch_database: Fixed disappearance of services caused by dynamically generated IDs

by Simon Betz

ID: 7127 Title: msexch_database: Fixed disappearance of services caused by dynamically generated IDs Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 After a reboot of the exchange server the databases get dynamically generated IDs. These IDs were part of the items which led to vanished services. This has been fixed now. You have to perform a re-discovery on the affected hosts.

5 years, 6 months

Check_MK Werk 7240: Fixed possible exception when filtering views using non ASCII characters

by Lars Michelsen

ID: 7240 Title: Fixed possible exception when filtering views using non ASCII characters Component: Multisite Level: 1 Class: Bug fix Version: 1.6.0i1 A GUI timeout or UnicodeDecodeError messages could occur when trying to filter views using non ASCII characters, like e.g. Umlauts. This could e.g. occur for users when trying to view service detail pages of services that have such characters in their names.

5 years, 6 months

Check_MK Werk 7046: cisco_temperature.dom: Make power levels configurable

by Florian Kromer

ID: 7046 Title: cisco_temperature.dom: Make power levels configurable Component: Checks & agents Level: 1 Class: New feature Version: 1.6.0i1 This werk adds support for power level configuration. Previously device configuration specific power levels have been used only which lead to an unexpected check status in case the devices have not been configured properly.

5 years, 6 months

Check_MK Werk 6658: Differentiation of host & service problems notifications

by Óscar Nájera

ID: 6658 Title: Differentiation of host & service problems notifications Component: Notifications Level: 1 Class: Bug fix Version: 1.6.0i1 For REST notification plugins like Slack, PagerDuty and VictorOPS. Problems where classified by the presence of the SERVICESTATE context variable. But in the RAW edition this variable is completed by its macro and thus the classification leads to host problems to be described as service problems too. Classifying after the WHAT context variable solves the issue.

5 years, 6 months

Check_MK Werk 7201: Servicenow: Notification plugin

by Ronny Bruska

ID: 7201 Title: Servicenow: Notification plugin Component: Notifications Level: 2 Class: New feature Version: 1.6.0i1 Check_MK now supports integration with Servicenow. You can create, update and close incidents for Host an Service Problems. Please see the inline help of the notification method rule within wato for detailed options. CMK-1167

5 years, 6 months

Check_MK Werk 7217: HW/SW-Inventory: Execution order of plugins

by Moritz Kiemer

ID: 7217 Title: HW/SW-Inventory: Execution order of plugins Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 The order in which the HW/SW inventory plugins are executed is now deterministic. Previously dependencies between inventory plugins could lead to missing data if the plugins happend to be executed in the wrong order. Plugins are now executed in alphabetical order by default. You can force a plugin to be executed after another plugin by setting the <tt>depends_on</tt> key in the inventory info variable <tt>inv_info</tt>. For instance writing <tt>inv_info['plugin_a'] = { ... 'depends_on' = ['plugin_b'], }</tt> will enforce "plugin_b" to be executed before "plugin_a".

5 years, 6 months

Check_MK Werk 7245: New builtin tag group "piggyback" allows to explictly turn piggyback data usage on/off

by Andreas Boesl

ID: 7245 Title: New builtin tag group "piggyback" allows to explictly turn piggyback data usage on/off Component: WATO Level: 1 Class: New feature Version: 1.6.0i1 Piggyback data is currently only read when the host has a Check_MK service. For some systems, the existance of the Check_MK service solely depends on the existance of piggyback files for the given host. During the config generation phase of the monitoring core, race conditions could apply, where a host might receive no Check_MK service. This werk introduces an explicit piggyback host tag, which allows you to enforce/disable the use of piggyback data. Per default this option is currently set to <tt>Automatically detect piggyback usage</tt>, to be compatible with the previous behaviour. You should explictly set the <tt>Use piggyback data</tt> option if you have a ping only host, which receives additional piggyback data from another host. This actively prevents beforementioned race conditions.

5 years, 6 months

Check_MK Werk 7050: nginx_status: Add missing metric definitions

by Florian Kromer

ID: 7050 Title: nginx_status: Add missing metric definitions Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 CMK-1766

5 years, 6 months

Check_MK Werk 7237: Increased size of host/service notes url input fields

by Lars Michelsen

ID: 7237 Title: Increased size of host/service notes url input fields Component: Multisite Level: 1 Class: Bug fix Version: 1.6.0i1

5 years, 6 months

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 March 2019