Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

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, 11 months

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, 11 months

Check_MK Werk 3920: Graphs: Vertical axis scaling and mirroring can now be customized

by Lars Michelsen

ID: 3920 Title: Graphs: Vertical axis scaling and mirroring can now be customized Component: Multisite Level: 2 Class: New feature Version: 1.5.0i1 You can now customize the vertical axis scaling mode and mirror the metrics in a graph if you like. This can be done just for yourself or for all your users. This can be useful, for example, if you like to change the scaling of all CPU usage graphs from fixed 100% to dynamical scaling based on the measured values. This feature is usable for all template based and combined graphs. It does not affect custom graphs at all. To configure such a customization open your GUI and click the {{Edit}} button of your {{Views}} snapin. Then click on the {{Graph tunings}} button on the top of the page. From this page you can then create a new graph tuning where you first need to set a title and the graph type you want to customize

7 years

Check_MK Werk 5122: Service discovery: Find SNMP checks of not yet monitored type when using cached data

by Simon Betz

ID: 5122 Title: Service discovery: Find SNMP checks of not yet monitored type when using cached data Component: WATO Level: 2 Class: Bug fix Version: 1.5.0i1

7 years

Check_MK Werk 5202: Fixed timeouts when generating reports (regression in #4957)

by Lars Michelsen

ID: 5202 Title: Fixed timeouts when generating reports (regression in #4957) Component: Reporting & Availability Level: 2 Class: Bug fix Version: 1.5.0i1 When creating PDF reports that contain grouped view elements, these reports were rendering too many data. In case of larger reports with a lot of graphs, this could lead to timeouts resulting in "Proxy Errors" messages in the GUI. This issue was introduced with werk 4957 since Check_MK 1.4.0p9.

7 years

Check_MK Werk 5185: Check_MK HW/SW Inventory: The service was executed too often by default

by Lars Michelsen

ID: 5185 Title: Check_MK HW/SW Inventory: The service was executed too often by default Component: HW/SW Inventory Level: 2 Class: Bug fix Version: 1.5.0i1 Issue: The HW/SW inventory may produce a lot of load because of wrong scheduling. You may be affected by this bug in case you created your (master) site with 1.4.0b1 or newer. If you updated your site from older versions you are likely not affected. Slave sites that get their configuration from a master that is not affected will also not be affected, regardless of the version they were created with. When using the hardware software inventory the regular check "Check_MK HW/SW Inventory" on each host is executed too often by default. The expected behaviour is that the regular check interval of this service is 1 day. The bug we fixed now made the check being executed once a minute. In case you have the HW/SW inventory enabled for a lot of hosts, this could lead to significant load on your Check_MK server. Whether or not you have this issue can be checked on the "service detail" page of the "Check_MK HW/SW Inventory" service. Have a look at the "Service normal/retry check interval" column where you should see 86400s as first value (-> 1 day). If you see a value of 60s, you should fix the issue as follows. <ul> <li>Navigate to "WATO > Host & Service parameters > Monitoring configuration > Normal check interval for service checks".</li> <li>Create a new rule with the following settings:</li> <li>Description: Restrict HW/SW-Inventory to once a day</li> <li>Value: 1 day</li> <li>Services: <tt>Check_MK HW/SW Inventory$</tt></li> <li>Activate the changes via WATO</li> <li> After this you should check the service detail page again and see the 86400s interval. Even when you update your existing site to 1.4.0p11 or newer, you will have to apply the fix manually to existing installations when your installation is affected. Sites created with 1.4.0p11 or newer won't be affected.

7 years

Check_MK Werk 5188: Sending service metrics to Graphite/InfluxDB can now be fine-tuned

by Sven Panne

ID: 5188 Title: Sending service metrics to Graphite/InfluxDB can now be fine-tuned Component: Core & setup Level: 2 Class: New feature Version: 1.5.0i1 Previously, there was a service rule to configure one of three levels of information to be sent to Graphite/InfluxDB: Send nothing, send only value, or send value/warn/crit/min/max. Now the rule is more fine-grained, so one can choose for each part of the metric if it should be sent or not. Furthermore, one can now send the unity of measurement, too.

7 years

Check_MK Werk 5176: CME: Custom design (Logo + color set) can now be set per customer

by Lars Michelsen

ID: 5176 Title: CME: Custom design (Logo + color set) can now be set per customer Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 It is now possible to customize the GUI design for each customer individually. The customer individual setting overrides the globally configured things.

7 years

Check_MK Werk 5175: Livestatus TCP: Can now be restricted to specific IP addresses

by Lars Michelsen

ID: 5175 Title: Livestatus TCP: Can now be restricted to specific IP addresses Component: Site Management Level: 2 Class: New feature Version: 1.5.0i1 When enabling livestatus access via TCP (via "omd config" or the WATO site management) it is now possible to restrict the access to a set of client IP addresses. The new option has been added to the global setting "Access to Livestatus via TCP" which then sets the "omd config" option LIVESTATUS_TCP_ONLY_FROM.

7 years

Check_MK Werk 5173: Major OMD config options can now be set via WATO global settings

by Lars Michelsen

ID: 5173 Title: Major OMD config options can now be set via WATO global settings Component: WATO Level: 2 Class: New feature Version: 1.5.0i1 The OMD configuration options that are used to configure basic aspects of the Check_MK sites can now be configured via WATO. The settings are available via "WATO > Global settings > Site Management". These settings are activated during regular activate changes similar to the other configuration settings. It is also possible to set site specific option via the site specific global settings.

7 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2