Checkmk werks level1 September 2016

checkmk-werks-lvl1@lists.checkmk.com

9 participants
79 discussions

Check_MK Werk 3862: mknotifyd mknotifyd.connection: New service description (when enabled)

by Lars Michelsen

ID: 3862 Title: mknotifyd mknotifyd.connection: New service description (when enabled) Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1 The checks were using an uncommon service description for their checks: Notification Spooler [site] ... Because those processes are logically tied to the OMD sites, it makes more sense to make them match the other OMD site check naming scheme: OMD [site] Notification Spooler This has now been changed. It will automatically be applied to new sites. Existing sites will only use this new description after enabling it via Global Settings and performing a rediscovery of the services on the affected hosts.

8 years

Check_MK Werk 3861: Introduced open event limit mechanism for protecting against message storms

by Lars Michelsen

ID: 3861 Title: Introduced open event limit mechanism for protecting against message storms Component: Event Console Level: 3 Class: New Feature Version: 1.4.0i1 The Event Console has been extended to be able to protect agains message storms which can either result in too high load and also in out of memory situations. Because there can be multiple kind of message storms like one device which sends a lot of messages or many different devices sending equal messages, we introduced different limits to match them. There are the following limits: <ul> <li>Limit by host: You can limit the number of open events created by a single host . This is meant to prevent you from message storms created by one device. Once the limit is reached, the Event Console will block all future incoming messages sent by this host until the number of open events has been reduced to be below this limit. In the moment the limit is reached, the Event Console will notify the configured contacts of the host.</li> <li>Limit by rule: You can limit the number of open events created by a single rule here. This is meant to prevent you from too generous rules creating a lot of events. Once the limit is reached, the Event Console will stop the rule creating new open events until the number of open events has been reduced to be below this limit. In the moment the limit is reached, the Event Console will notify the configured contacts of the rule or create a notification with empty contact information.</li> <li>Overall limit: To protect you against a continously growing list of open events created by different hosts or rules, you can configure this overall limit of open events. All currently open events are counted and once the limit is reached, no further events will be opened which means that new incoming messages will be dropped. In the moment the limit is reached, the Event Console will create a notification with empty contact information. </li> </ul> Each of those limits can be configured to different values. By default the limit is set to 1000 for the host and rule based limit and 10000 for the overall limit. Please check carefully whether or not these defaults are OK for you. But they should be way enough for most environments since you really should never have so many open events in the Event Console open. But if you need to change those limits, you can change them in the global settings of the Event Console to fit your needs. Additionally, you can configure the actions the Event Console should perform once the limit is reached instead of the overflow event and notification creation as described above. Another action is for example delete the oldest event (of a host, rule or overall).

8 years

Check_MK Werk 3746: tinkerforge: Keep check from crashing in case of unconfigured params

by Konstantin Büttner

ID: 3746 Title: tinkerforge: Keep check from crashing in case of unconfigured params Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1

8 years

Check_MK Werk 3839: filehandler: added new plugin for monitoring file handles in linux

by Marcel Arentz

ID: 3839 Title: filehandler: added new plugin for monitoring file handles in linux Component: Checks & Agents Level: 1 Class: New Feature Version: 1.4.0i1 This new plugin reads file handles provided by /proc/sys/fs/file-nr and puts them in relation of each other. Thresholds of this check can be configured. Defaults are on 80/90%.

8 years

Check_MK Werk 3838: hitachi_hus_dku & hitachi_hus_dkc: more detailed output even if everything is in state OK

by Marcel Arentz

ID: 3838 Title: hitachi_hus_dku & hitachi_hus_dkc: more detailed output even if everything is in state OK Component: Checks & Agents Level: 1 Class: New Feature Version: 1.4.0i1 The outputs of these Checks are more verbose even if there is no failure of one or more components. So now it is always transparent which components are checked an in which state they are.

8 years

Check_MK Werk 3805: WATO WebAPI: The configuration of cluster nodes is now officially supported

by Andreas Boesl

ID: 3805 Title: WATO WebAPI: The configuration of cluster nodes is now officially supported Component: WATO Level: 1 Class: New Feature Version: 1.4.0i1 You can now set the new key <tt>nodes</tt> in the add_host and edit_host operations. The value is a list of cluster node names. A host is treated as normal host if the key is entirely missing or if the node list is empty.

8 years

Check_MK Werk 3860: EC condition: Fixed default value of rule id selection

by Lars Michelsen

ID: 3860 Title: EC condition: Fixed default value of rule id selection Component: Notifications Level: 1 Class: Bug Fix Version: 1.4.0i1

8 years

Check_MK Werk 3859: check_mail_loop.vbs: New MRPE script to perform a mail loop check via Outlook MAPI

by Lars Michelsen

ID: 3859 Title: check_mail_loop.vbs: New MRPE script to perform a mail loop check via Outlook MAPI Component: Checks & Agents Level: 1 Class: New Feature Version: 1.4.0i1 The check is similar to the default check_mail_loop active check (which can be configured via WATO), but it works using Outlook and the MAPI protocol to send and receive mails. So you can construct a mail loop checking your Exchange mail infrastrucure without involving other protocols like IMAP, POP3 or SMTP. Take a look at the file header of the script. It describes how to setup the script.

8 years

Check_MK Werk 3701: FIX ps.perf graph title for Memory and CPU Usage

by Marcel Schulte

ID: 3701 Title: FIX ps.perf graph title for Memory and CPU Usage Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1 Fixed graph titles to show "Usage for all processes".

8 years

Check_MK Werk 3803: netapp_api_connection: reports any errors happened during the collection of data

by Andreas Boesl

ID: 3803 Title: netapp_api_connection: reports any errors happened during the collection of data Component: Checks & Agents Level: 1 Class: New Feature Version: 1.4.0i1 This check shows insufficient user permissions or invalid user credentials as warnings. You can setup a WATO rule which can change the warning message(s) to an other state.

8 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 September 2016