Checkmk werks level2 October 2017

checkmk-werks-lvl2@lists.checkmk.com

2 participants
18 discussions

Check_MK Werk 5359: Reduced size of PDF exports containing graphs

by Lars Michelsen

ID: 5359 Title: Reduced size of PDF exports containing graphs Component: Reporting & Availability Level: 2 Class: Bug fix Version: 1.5.0i1 The size of PDF exports increased dramatically when graphs were shown. This was caused by the gradients used in the rendered metric areas. For example a PDF with 10 graphs had a size of 6 MB with gradients compared to 260 KB without gradients. The gradients have now been dropped completely.

6 years, 10 months

Check_MK Werk 5363: Exporting graph data in JSON format via GUI is now possible

by Lars Michelsen

ID: 5363 Title: Exporting graph data in JSON format via GUI is now possible Component: Multisite Level: 2 Class: New feature Version: 1.5.0i1 When viewing a graph in the GUI it is now possible to open the context menu and click on "Export as JSON" to get the data that is shown in the graph as JSON output.

6 years, 10 months

Check_MK Werk 5234: Fixed recently introduced issue with non working WATO rules

by Andreas Boesl

ID: 5234 Title: Fixed recently introduced issue with non working WATO rules Component: Checks & agents Level: 2 Class: Bug fix Version: 1.5.0i1 In 1.4.0p14 an internal caching mechanism was changed. This broke some caches and caused unexpected behaviours, because most configurable rules were considered as empty.

6 years, 10 months

Check_MK Werk 5392: Fixed host monitored from all sites after editing custom host attributes

by Lars Michelsen

ID: 5392 Title: Fixed host monitored from all sites after editing custom host attributes Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1 In distributed environments it could happen that all configured hosts are monitored from all configured sites. The now fixed issue was triggered by saving (adding/editing/removing) custom host attributes using the "WATO > Hosts > Custom host attributes" dialog. Background: This editing step was undeclaring the internal "site" attribute by accident and rewriting all hosts.mk files. These files were missing the "site:..." host tag in the all_hosts data structure. This makes all sites think that they are responsible for these hosts. The configured site information of the hosts/folders was not lost because it was retained in the host_attributes data strucuture. So the hosts.mk files could be "repaired" by saving the hosts, parent folders or host tags.

6 years, 10 months

Check_MK Werk 5397: Microcore can now be configured to send UNREACHABLE notifications

by Lars Michelsen

ID: 5397 Title: Microcore can now be configured to send UNREACHABLE notifications Component: Core & setup Level: 2 Class: New feature Version: 1.5.0i1 Normally you don't want to receive UNREACHABLE notifications of hosts. Configuring client/parent relationships between your hosts is a good idea to be able to detect network outages. DOWN states of hosts will then be translated into UNREACHABLE, making your view clear for the real cause (e.g. a router in DOWN state). But there may be situations where you want to be able to receive these UNREACHABLE notifications. This was already configurable when using the Nagios core for a long time. For the Microcore the suppression of UNREACHABLE notifications was hard coded. This has been changed now. The default behaviour will not be changed. New sites or updates sites will not send out UNREACHABLE notifications by default. To enable the new feature, you will first have to tell the core to send out UNREACHABLE notifications. To have a seamless transition we additionally changed these things: <ul> <li>A default rule that disables the UNREACHABLE notifications is being created for new sites in the ruleset "Notified events for hosts". Whenever you want to enable UNREACHABLE notifications, simply enable them using this rule.</li> <li>Updated sites: <ul> <li>If you have configured rules for all your hosts in the "Notified events for hosts" ruleset, the core will continue working as configured.</li> <li>Microcore: For hosts that have no matching rule in "Notified events for hosts", the Microcore will <i>not send</i> out UNREACHABLE notifications.</li> <li>Microcore: If you previously had configured a rule in "Notified events for hosts" which enabled the UNREACHABLE notifications, this rule had no effect. It will now be working after updating.</li> <li>Nagios: For hosts that have no matching rule in "Notified events for hosts", the Nagios core will <i>send</i> out UNREACHABLE notifications.</li> </ul> </li> </ul>

6 years, 10 months

Check_MK Werk 5236: Edit host/service/contactgroups: Fixed exception in CME, improved audit logging

by Andreas Boesl

ID: 5236 Title: Edit host/service/contactgroups: Fixed exception in CME, improved audit logging Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1

6 years, 10 months

Check_MK Werk 4753: Inactive browser windows/tabs are not updated until focused again

by Lars Michelsen

ID: 4753 Title: Inactive browser windows/tabs are not updated until focused again Component: Multisite Level: 2 Class: New feature Version: 1.5.0i1 This change should be a performance improvement to reduce the load of the sites webserver. While a Check_MK GUI page is opened in the browser several parts are updating themselfs in the background, for example sidebar snapins, dashlets and views. A lot of users open several instances of the GUI in different browser tabs (or windows) and leave them inactive in the background. They open different tabs and keep the others in background or even leave their computer running and just lock their user session. In such situation the browser keeps updating the page elements even when no one looks at the information. We have now implemented a mechanism to detect whether or not a page is visible or hidden to the user. In later case the updates are stopped until the user opens the page again, then the updates are immediately done. This change should be seamless for the user in most cases because the updates are immediately done when the user focuses the page again, but it might happen that you see a "grayed out" page for a short time. This grayed out page visualizes that the information is outdated. If you should see this for several seconds there is something wrong. But you can always tell your browser to reload the page which should resolve this.

6 years, 10 months

Check_MK Werk 5402: Number of apache processes can now be configured via Global Settings

by Lars Michelsen

ID: 5402 Title: Number of apache processes can now be configured via Global Settings Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 It is now possible to configure the apache configuration option {MaxClients} via WATO (Global Settings > Site Management > Apache process tuning). This option is often changed to tune the site apache to either consume less memory (reduce the number of maximum processes) or being able to handle more users in the GUI simultaneously. The option can be configured globally for all sites or in the site specific globals, depending on your needs. The defaul value of this option is read from the existing configuration files (etc/apache/apache.conf and etc/apache/conf.d/*.conf) and defaults to {64}.

6 years, 10 months

Check_MK Werk 5403: RRDCached tuning can now be configured via Global Settings

by Lars Michelsen

ID: 5403 Title: RRDCached tuning can now be configured via Global Settings Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 It is now possible to configure the tuning settings of the rrdcached via WATO (Global Settings > Site Management > RRDCached tuning). This option is often changed to tune the disk IO behavious of the RRDCached. Details about this can be found here: http://mathias-kettner.de/cms_graphing.html The option can be configured globally for all sites or in the site specific globals, depending on your needs. The default values of the options are read from the existing configuration files (etc/rrdcached.conf and etc/rrdcached.d/*.conf).

6 years, 10 months

Check_MK Werk 5403: RRDCached tuning can now be configured via Global Settings

by Lars Michelsen

6 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2 October 2017