Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 4818: Fixed "No Data" in Tactical Overview if missing permissions to see failed notifications

by Marcel Arentz

ID: 4818 Title: Fixed "No Data" in Tactical Overview if missing permissions to see failed notifications Component: Multisite Level: 2 Class: Bug fix Version: 1.5.0i1 Guest do not have permissions to see failed notifications per default which lead into an empty tactical overview. This bug is in Check_MK since June 2016.

7 years, 3 months

Check_MK Werk 4780: HW/SW inventory: Removed entries about section ages provided by check_mk_agent; this reverts Werk 3904

by Simon Betz

ID: 4780 Title: HW/SW inventory: Removed entries about section ages provided by check_mk_agent; this reverts Werk 3904 Component: HW/SW Inventory Level: 2 Class: Bug fix Version: 1.5.0i1 These HW/SW inventory entries filled up inventory archive and slowed down the monitoring system. See also Werk 4485.

7 years, 3 months

Check_MK Werk 8656: Button "All Logfiles" in logwatch user interface now works in distributed mode

by Mathias Kettner

ID: 8656 Title: Button "All Logfiles" in logwatch user interface now works in distributed mode Component: Multisite Level: 2 Class: Bug fix Version: 1.5.0i1 The problem was that this button would only show the log files that are on the same monitoring site as the currently shown log file or host. This problem only appeared in a distributed environment.

7 years, 3 months

Check_MK Werk 4711: mknotifyd: parts of master configuration could be transfered to the slave sites

by Andreas Boesl

ID: 4711 Title: mknotifyd: parts of master configuration could be transfered to the slave sites Component: Notifications Level: 2 Class: Bug fix Version: 1.5.0i1 Global configuration settings for the master site, which were configured through the Distributed Monitoring page, were transfered to any slave sites. This caused problems on the mknotifyd running on the slave sites. This has been fixed.

7 years, 3 months

Check_MK Werk 4788: openhardwaremonitor: New support of current hardware

by Marcel Arentz

ID: 4788 Title: openhardwaremonitor: New support of current hardware Component: Checks & agents Level: 2 Class: Bug fix Version: 1.5.0i1 Due the update from 0.7.1 to 0.8.0 a new set of hardware is supported. For more information please see the official website of the developer: http://openhardwaremonitor.org/

7 years, 3 months

Check_MK Werk 4703: Business intelligence: fixed various display and navigation bugs in timelines page

by Andreas Boesl

ID: 4703 Title: Business intelligence: fixed various display and navigation bugs in timelines page Component: BI Level: 2 Class: Bug fix Version: 1.5.0i1 <ul> <li>Fixed from/until computation error</li> <li>No longer hiding timewarped aggregations (BI aggregations at selected timestamps)</li> <li>Fixed missing/redundant navigation arrows in the timeline selection</li> <li>Disabled support for multiple BI aggregations in timeline page. This feature will be redesigned later on</li> </ul>

7 years, 3 months

Check_MK Werk 4701: WATO Web-API: now able to manage sites

by Andreas Boesl

ID: 4701 Title: WATO Web-API: now able to manage sites Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 You can now configure the WATO sites through new API calls <ul> <li>get_site: requires the site_id key in the request object</li> <li>set_site: expects the same data format, than the get_site call provides.</li> <li>delete_site: requires the site_id key in the request object</li> <li>login_site: requires the site_id, the username and the password keys in the request object</li> <li>logout_site: requires the site_id key in the request object</li> </ul> Important: Right now the interface is only able to speak the python language. The existing output_format parameter, as well as the new request parameter <tt>request_format</tt> must both be set to <tt>python</tt>. An additional interface language is planned, maybe XML. Furthermore, these API calls are intended for admin use only, since they might modify the entire site configuration object.

7 years, 3 months

Check_MK Werk 4700: WATO Web-API: Now able to configure host tags

by Andreas Boesl

ID: 4700 Title: WATO Web-API: Now able to configure host tags Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 You can now configure the WATO Hosttags through the new API calls <tt>get_hosttags</tt> and <tt>set_hosttags</tt>. Important: These API calls are intended for admin use only, since they modify the entire hosttags configuration. <tt>get_hosttags</tt> This API call does not require any additional info. It simply returns a dictionary with all tag_group and aux_tags. The response also includes an extra key <tt>configuration_hash</tt>, which can be used in the following call. <tt>set_hosttags</tt> The previous call provided a dict with the hosttags configuration. This call expect the same format in the request object. You can modify the modify the previously queried dict and send it back. If you also sent the configuration_hash parameter, the Web-API will check if the configuration has changed in the meantime. If so, the set_hosttags call will fail. When no configuration_hash parameter is sent, no checking will be done and the configuration is completely overwritten. However, there are some final checks before the configuration is applied. First of all, the syntax and dependencies are checked. Furthermore, the api call checks whether all explicitely configured host tags are still present in the updated configuration. You can not set hosttags when the operation would introduce corrupt host tag settings.

7 years, 3 months

Check_MK Werk 4699: WATO Web-API: now able to configure rulesets

by Andreas Boesl

ID: 4699 Title: WATO Web-API: now able to configure rulesets Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 You can now configure all rules which are available in the Host & Service Parameters Page through the use of two Web-API calls. Important: Right now the interface is only able to speak the python language. The existing output_format parameter, as well as the new request parameter <tt>request_format</tt> must both be set to <tt>python</tt>. An additional interface language is planned, maybe XML. Furthermore, these API calls are intended for admin use only, since they modify the entire ruleset in all folders. <tt>get_rulesets_info</tt> This API call does not require any additional info. It simply returns a list of all available rulesets. Each entry of this list is a dictionary which includes information about the title, the help text, the item help text and the how often the rule is used. <tt>get_ruleset</tt>br> Requires the request key <tt>ruleset_name</tt>, which specifies the ruleset to query. This API call returns exactly one complete ruleset of all folders, so you can't query differnt types. The response itself has an extra key configuration_hash, which can be used in the following call. <tt>set_ruleset</tt>br> The previous call provided a dict with the ruleset configuration. This call expect the same format in the request object. You can modify the modify the previously queried dict and send it back through this f you also sent the configuration_hash parameter, the Web-API will check if the configuration has changed in the meantime. If so, the set_ruleset call will fail. When no configuration_hash parameter is sent, no checking will be done.

7 years, 4 months

Check_MK Werk 4567: inventory of interfaces: prevent showing negative last_state_change value

by Marcel Schulte

ID: 4567 Title: inventory of interfaces: prevent showing negative last_state_change value Component: HW/SW Inventory Level: 2 Class: Bug fix Version: 1.5.0i1 On SNMP devices sysUpTime is a 32-bit counter and will roll over after 496 days. ifLastChange is the timestamp from sysUpTime when the state changed. At inventory time we got a negative value if sysUpTime was smaller then ifLastChange (because it rolled over) using the normal formula. If sysUpTime is smaller than ifLastChange we add 496 days for the rollover now. When the device reboots all last_state_change values are set to 0 by the device so those cases are not affected by the fix.. Beware there's no way to get the count of times the sysUpTime counter rolled over so the last_state_change is not accurate in case it's in real more than 496 days ago. ...but this situation has never been different. This fix just removes another error in shown values.

7 years, 4 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2