Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15940 discussions

Check_MK Werk 3810: windows agent: no longer truncates plugin output, no longer freezes when plugin produces too much output

by Andreas Boesl

ID: 3810 Title: windows agent: no longer truncates plugin output, no longer freezes when plugin produces too much output Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1 Contains two bugfixes. Fixed race condition where data from a script was not completely read from the suprocess's pipes. Fixed an agent freeze when the plugin data exceeded 2MB.

8 years

Check_MK Werk 3876: new option "negation" for filter "several service groups"

by Simon Betz

ID: 3876 Title: new option "negation" for filter "several service groups" Component: Multisite Level: 1 Class: New Feature Version: 1.4.0i1

8 years

Check_MK Werk 3808: df.include: fixed incorrect levels calculations on very small filesystems

by Andreas Boesl

ID: 3808 Title: df.include: fixed incorrect levels calculations on very small filesystems Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1 Filesystems with <tt>Free space left</tt> levels less than 1MB were incorrectly calculated. The check always reported CRIT in this scenario.

8 years

Check_MK Werk 3807: mssql_counters: fixed crash when the check is unable to parse a timestamp provided by the plugin

by Andreas Boesl

ID: 3807 Title: mssql_counters: fixed crash when the check is unable to parse a timestamp provided by the plugin Component: Checks & Agents Level: 1 Class: Bug Fix Version: 1.4.0i1

8 years

Check_MK Werk 3885: Fixed sorting of version in werk list (1.2.8p10 and 1.2.8p11 were not listed on top)

by Lars Michelsen

ID: 3885 Title: Fixed sorting of version in werk list (1.2.8p10 and 1.2.8p11 were not listed on top) Component: Multisite Level: 1 Class: Bug Fix Version: 1.4.0i1

8 years

Check_MK Werk 3875: tsm_stagingpools: check is now cluster aware

by Simon Betz

ID: 3875 Title: tsm_stagingpools: check is now cluster aware Component: Checks & Agents Level: 1 Class: New Feature Version: 1.4.0i1

8 years

Check_MK Werk 3806: Sped up "Activate changes"

by Andreas Boesl

ID: 3806 Title: Sped up "Activate changes" Component: Core & Setup Level: 1 Class: New Feature Version: 1.4.0i1 Introduced caching for many regularly called functions. As a result, the config generation for the core should be at least 2-3 times faster. Note: The computation time highly depends on the number of used rules and hosts.

8 years

Check_MK Werk 3884: Notifications: Fixed wrong LASTSERVICESTATE and SERVICESTATE in EC notifications

by Lars Michelsen

ID: 3884 Title: Notifications: Fixed wrong LASTSERVICESTATE and SERVICESTATE in EC notifications Component: Event Console Level: 1 Class: Bug Fix Version: 1.4.0i1 The variables LASTSERVICESTATE had CRIT instead of CRITICAL and the SERVICESTATE variable had WARN instead of WARNING and CRIT instead of CRITICAL values set.

8 years

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1