Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15970 discussions

Check_MK Werk 5236: Edit host/service/contactgroups: Fixed exception in CME, improved audit logging

by Andreas Boesl

ID: 5236 Title: Edit host/service/contactgroups: Fixed exception in CME, improved audit logging Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1

6 years, 11 months

Check_MK Werk 5304: mssql_backup: Fixed error if existing rule has been set before 1.5.0

by Marcel Arentz

ID: 5304 Title: mssql_backup: Fixed error if existing rule has been set before 1.5.0 Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1 In werk #4811 the ruleset for mssql_backup has been extended. Since then the GUI would crash if a rule has been set up previously to this update. This has been fixed now.

6 years, 11 months

Check_MK Werk 5303: local: Fixed missing warn/crit in graphs if upper and lower thresholds are in perfdata

by Marcel Arentz

ID: 5303 Title: local: Fixed missing warn/crit in graphs if upper and lower thresholds are in perfdata Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1 A graph did not display warn/crit values if there has been upper and lower thresholds in the perfdata of a local check. The cause of this has been a colon in between these values. The upper thresholds are represented in a graph now.

6 years, 11 months

Check_MK Werk 5398: Agent bakery: Hide "Bake Agents" context button when not permitted to bake

by Lars Michelsen

ID: 5398 Title: Agent bakery: Hide "Bake Agents" context button when not permitted to bake Component: WATO Level: 1 Class: Bug fix Version: 1.5.0i1

6 years, 11 months

Check_MK Werk 5345: mssql_backup: fix GUI error and show warn/crit values

by Tom Baerwinkel

ID: 5345 Title: mssql_backup: fix GUI error and show warn/crit values Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1 Fixes an error visible in the GUI when no parameters are present for the check. The check now also shows warn and crit values for a backup type if it is in a warning or critical state.

6 years, 11 months

Check_MK Werk 5321: mk_oracle: Fixed usage of awk command in case of SunOS which causes 'record ... too long' error

by Simon Betz

ID: 5321 Title: mk_oracle: Fixed usage of awk command in case of SunOS which causes 'record ... too long' error Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1 The consequence of above error was that Check_MK did not find any ORACLE instances any more. Fixed that by using {{nawk}} in case of SunOS.

6 years, 11 months

Check_MK Werk 5397: Microcore can now be configured to send UNREACHABLE notifications

by Lars Michelsen

ID: 5397 Title: Microcore can now be configured to send UNREACHABLE notifications Component: Core & setup Level: 2 Class: New feature Version: 1.5.0i1 Normally you don't want to receive UNREACHABLE notifications of hosts. Configuring client/parent relationships between your hosts is a good idea to be able to detect network outages. DOWN states of hosts will then be translated into UNREACHABLE, making your view clear for the real cause (e.g. a router in DOWN state). But there may be situations where you want to be able to receive these UNREACHABLE notifications. This was already configurable when using the Nagios core for a long time. For the Microcore the suppression of UNREACHABLE notifications was hard coded. This has been changed now. The default behaviour will not be changed. New sites or updates sites will not send out UNREACHABLE notifications by default. To enable the new feature, you will first have to tell the core to send out UNREACHABLE notifications. To have a seamless transition we additionally changed these things: <ul> <li>A default rule that disables the UNREACHABLE notifications is being created for new sites in the ruleset "Notified events for hosts". Whenever you want to enable UNREACHABLE notifications, simply enable them using this rule.</li> <li>Updated sites: <ul> <li>If you have configured rules for all your hosts in the "Notified events for hosts" ruleset, the core will continue working as configured.</li> <li>Microcore: For hosts that have no matching rule in "Notified events for hosts", the Microcore will <i>not send</i> out UNREACHABLE notifications.</li> <li>Microcore: If you previously had configured a rule in "Notified events for hosts" which enabled the UNREACHABLE notifications, this rule had no effect. It will now be working after updating.</li> <li>Nagios: For hosts that have no matching rule in "Notified events for hosts", the Nagios core will <i>send</i> out UNREACHABLE notifications.</li> </ul> </li> </ul>

6 years, 11 months

Check_MK Werk 5344: fileinfo: correct handling of file names with spaces in fileinfo.cfg

by Tom Baerwinkel

ID: 5344 Title: fileinfo: correct handling of file names with spaces in fileinfo.cfg Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i1

6 years, 11 months

Check_MK Werk 5396: Nagios: Log external commands to nagios.log by default

by Lars Michelsen

ID: 5396 Title: Nagios: Log external commands to nagios.log by default Component: Core & setup Level: 1 Class: Bug fix Version: 1.5.0i1 Nagios is now logging external commands to the core log (nagios.log) in the default configuration. This makes Nagios behave like the Microcore in this case.

6 years, 11 months

Check_MK Werk 5395: Nagios: Enable passive host check translation by default

by Lars Michelsen

ID: 5395 Title: Nagios: Enable passive host check translation by default Component: Core & setup Level: 1 Class: Bug fix Version: 1.5.0i1 The monitoring cores Nagios and Microcore where treating "fake check results" that can be sent from the GUI differently. These fake check results are in fact passive host checks. From these passive host checks Nagios simply takes over the reported state and uses it as new host state, ignoring the parent logic. The microcore takes the parent logic into account and may change a DOWN check result to UNREACHABLE when all parents are down. We have now changed the configuration option <tt>translate_passive_host_checks</tt> of Nagios to be enabled by default to make Nagios also check this logic.

6 years, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1