Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15984 discussions

Check_MK Werk 5845: fsc checks: prevent fsc_fans and fsc_temp if corresponding fsc_sc2-* data is available, made snmp_scan_functions more readable

by Marcel Schulte

ID: 5845 Title: fsc checks: prevent fsc_fans and fsc_temp if corresponding fsc_sc2-* data is available, made snmp_scan_functions more readable Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 * fsc_fans and fsc_temp do not discover services anymore, if corresponding fsc_sc2_* data is available. * snmp_scan_functions were made more readable using functions in fsc.include

6 years

Check_MK Werk 6629: jolokia_generic: Make service descriptions consistent with jolokia_metrics

by Konstantin Büttner

ID: 6629 Title: jolokia_generic: Make service descriptions consistent with jolokia_metrics Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1 Rediscovery is required on the affected hosts.

6 years

Check_MK Werk 6628: Improved timeperiod management

by Lars Michelsen

ID: 6628 Title: Improved timeperiod management Component: WATO Level: 2 Class: New feature Version: 1.6.0i1 The timeperiod management pages have been improved ins several ways: <ul> <li>Timeperiods can now be cloned.</li> <li>Configuring equal times for all weekdays is now easier. Instead of setting the same time ranges for each weekday it is now possible to select "Same times for all week days".</li> <li>Timeperiods listed in the excludes list are now sorted.</li> <li>The number of time ranges per day is now flexible. The dialog starts with a single time range. You may click on "add time range" to add more.</li> <li>Improved validations of input values.</li> <li>The builtin timeperiod 24X7 is now always visible. The implicit existance of this timeperiod confused users.</li> </ul>

6 years

Check_MK Werk 6660: Background Jobs: fixed issue with monitoring sites running on nfs mount

by Andreas Boesl

ID: 6660 Title: Background Jobs: fixed issue with monitoring sites running on nfs mount Component: WATO Level: 1 Class: Bug fix Version: 1.6.0i1 If the site is running on a nfs mount, the background job could crash during a directory cleanup. This was caused by an open file handle within the designated directory.

6 years

Check_MK Werk 6715: Editing BI Rules: Increased size of the rule ID input field

by Lars Michelsen

ID: 6715 Title: Editing BI Rules: Increased size of the rule ID input field Component: WATO Level: 1 Class: Bug fix Version: 1.6.0i1

6 years

Check_MK Werk 6714: docker_container_status: Fixed possible "ValueError" exception

by Lars Michelsen

ID: 6714 Title: docker_container_status: Fixed possible "ValueError" exception Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0i1

6 years

Check_MK Werk 6662: Timespecific check parameters: Changed computation algorithm to allow more flexible configurations

by Andreas Boesl

ID: 6662 Title: Timespecific check parameters: Changed computation algorithm to allow more flexible configurations Component: WATO Level: 2 Class: New feature Version: 1.6.0i1 Werk #4840 introduced timespecific parameters, which allowed timedependant check parameter configuration through timeperiods. Customer feedback has shown that these configuration were not flexible enough. Thats why we've changed the computation algorithm. The new algorithm only affects dictionary based check parameters, tuple based check parameters remain unchanged. H3:Ruleset example old configuration (deprecated with this werk) <ul> <li>Use parameters {"warn": 90} on saturday, default {"warn": 75, "crit": 80}</li> <li>Use parameters {"warn": 85, "crit": 92"} on weekend, default {"warn": 70, "crit": 75, "bandwidth": 1000}</li> <li>Use parameters {"check_mode": "auto"} (no timespecific rule)</li> </ul> The old mechanism created the following parameters <ul> <li>Monday till Friday: {"warn": 75, "crit": 80"}</li> <li>Saturday: {"warn": 90}</li> <li>Sunday: {"warn": 75, "crit": 80}</li> </ul> As you can see, only the parameters from the first rule were taken into account. H3:Ruleset example new configuration <ul> <li>Use parameters {"warn": 90} on saturday, default {"warn": 75, "crit": 80}</li> <li>Use parameters {"warn": 85, "crit": 92"} on weekend, default {"warn": 70, "crit": 75, "bandwidth": 1000}</li> <li>Use parameters {"check_mode": "auto"} (no timespecific rule)</li> </ul> The new mechanism now creates the following parameters <ul> <li>Monday till Friday: {"warn": 75, "crit": 80", "check_mode": "auto"}</li> <li>Saturday: {"warn": 90, "crit": 80, "bandwith": 1000, "check_mode": "auto"}</li> <li>Sunday: {"warn": 85, "crit": 92, "bandwith": 1000, "check_mode": "auto"}</li> </ul> As you can see, only the parameters from the first rule were taken into account. The rule evaluation now starts at the bottom rule and then progresses to the top rule. For each rule, first of all the default parameters are applied. Afterwards the timespecific component(s) are applied. If a single rule have more than one timespecific parameter, these parameters are merged, too. For example: <ul> <li>Use parameters {"warn": 75, "crit": 80, "check_mode": "auto"} on Saturday 10-14h, Use parameters {"special_parameter": True} on Saturday 12-14h</li> <li>Use parameters {"warn": 85, "crit": 92"} on weekend, default {"warn": 70, "crit": 75, "bandwidth": 1000}</li> <li>Use parameters {"check_mode": "auto"} (no timespecific rule)</li> </ul> Result <ul> <li>Saturday 11:00: {"warn": 75, "crit": 80, "bandwidth": 1000, "check_mode": "auto"}</li> <li>Saturday 13:00: {"warn": 75, "crit": 80, "bandwidth": 1000, "check_mode": "auto", "special_parameter": True}</li> </ul>

6 years

Check_MK Werk 6468: docker_node_network: Fix crashing HW/SW inventory when labels are not set

by Konstantin Büttner

ID: 6468 Title: docker_node_network: Fix crashing HW/SW inventory when labels are not set Component: HW/SW Inventory Level: 1 Class: Bug fix Version: 1.6.0i1

6 years

Check_MK Werk 6573: Azure Monitoring

by Moritz Kiemer

ID: 6573 Title: Azure Monitoring Component: Checks & agents Level: 1 Class: New feature Version: 1.6.0i1 This werk adds a new datasource program to monitor Microsoft Azure cloud environments.

6 years

Check_MK Werk 6570: azure_sites: New Check to monitor azure web servers

by Moritz Kiemer

ID: 6570 Title: azure_sites: New Check to monitor azure web servers Component: Checks & agents Level: 1 Class: New feature Version: 1.6.0i1 This werk adds a check to monitor IIS web servers in the Azure cloud.

6 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1