Checkmk werks level1 November 2015

checkmk-werks-lvl1@lists.checkmk.com

7 participants
109 discussions

Check_MK Werk 2707: winperf_processor: can now be configured to warn if a single cpu core exceeds a utilization threshold for a while

by Sebastian Herbord

ID: 2707 Title: winperf_processor: can now be configured to warn if a single cpu core exceeds a utilization threshold for a while Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i4 This is the same feature as werk #2529, now for windows hosts.

8 years, 10 months

Check_MK Werk 2445: ibm_svc_disks: fixed crash in case special agent reports too much data columns per line

by Andreas Boesl

ID: 2445 Title: ibm_svc_disks: fixed crash in case special agent reports too much data columns per line Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.2.7i4

8 years, 10 months

Check_MK Werk 2720: nullmailer_mailq: New check for monitoring the outgoing mail queue of Nullmailer

by Lars Michelsen

ID: 2720 Title: nullmailer_mailq: New check for monitoring the outgoing mail queue of Nullmailer Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i4 This check monitors the number of mails in the deferred / outgoing mail queue of the Nullmailer daemon.

8 years, 10 months

Check_MK Werk 2719: Events Check: Links to EC were broken when using regular expressions as application

by Lars Michelsen

ID: 2719 Title: Events Check: Links to EC were broken when using regular expressions as application Component: Event Console Level: 1 Class: Bug Fix Version: 1.2.7i4 When using a regular expression to find Event Console events for an "Events" service, the icon linking from the service to the Event Console linked to a view which did not show the corrent amount of events.

8 years, 10 months

Check_MK Werk 2718: Fixed agent timeouts not resulting in a crash report anympore

by Lars Michelsen

ID: 2718 Title: Fixed agent timeouts not resulting in a crash report anympore Component: Core & Setup Level: 1 Class: Bug Fix Version: 1.2.7i4 When an agents takes too long to respond, this results in a timeout exception which was handled as "crash". This has been changed to output a proper error message.

8 years, 10 months

Check_MK Werk 2444: lnx_if: now able to detect interfaces which "break" during runtime

by Andreas Boesl

ID: 2444 Title: lnx_if: now able to detect interfaces which "break" during runtime Component: Checks & Agents Level: 1 Class: New Feature Version: 1.2.7i4 Previously the check lnx_if used the output of the ethtool command to determine if an interface is up or down. There was a fallback in case ethtool was not available, or did not report valid data at all (happens on broken interfaces). However, these fallback could not detect interfaces which break during runtime. The linux agent now reports additional information collected with the ip link command. In case the ethtool information is missing the lnx_if check will now use the data from ip link instead.

8 years, 10 months

Check_MK Werk 2443: Fixed quoting of ! in classical nagios checks configured via WATO

by Andreas Boesl

ID: 2443 Title: Fixed quoting of ! in classical nagios checks configured via WATO Component: Core & Setup Level: 1 Class: Bug Fix Version: 1.2.7i4 Any ! character configured in the WATO rule Classical active and passive Monitoring checks or through the command line via custom_checks was incorrectly quoted. Nagios truncated the command at the !, which lead to unwanted results.

8 years, 10 months

Check_MK Werk 2442: WATO remove host: improved cleanup of obsolete host files

by Andreas Boesl

ID: 2442 Title: WATO remove host: improved cleanup of obsolete host files Component: WATO Level: 1 Class: New Feature Version: 1.2.7i4 Deleting a host in WATO will now also remove the following files <ul> <li>Persisted data</li> <li>Piggyback data</li> <li>Inventory data</li> <li>Agent Bakery symlinks</li> </ul> To prevent the loss of historic files, any performance data and the archived inventory data is not deleted.

8 years, 10 months

Check_MK Werk 2733: Visibility of Event Console events more flexible now

by Mathias Kettner

ID: 2733 Title: Visibility of Event Console events more flexible now Component: Event Console Level: 1 Class: New Feature Version: 1.2.7i4 The assignment of Event Console events to contact groups is a bit more flexible now. There is a new global option in User Interface called Precedence of contact groups of events. The default setting is Host's contact groups have precedence and implements the previos behaviour. You now can change that to Contact groups in rule have precedence. This handles the case where an event can successfully be mapped to a host in the monitoring while there are specified explicit contact groups in the event rule. Those will have then precedence and not only be used as a fall back. That way you can explicitely assign events to arbitrary contact groups and by that way control the visibility. Note: this has now influence on notification.

8 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 November 2015