Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 5591: Only load graphs that are currently visible

by Lars Michelsen

ID: 5591 Title: Only load graphs that are currently visible Component: metrics Level: 2 Class: New feature Version: 1.5.0i3 With this change the graphs shown by the GUI are only rendered when they are (partially) visible to the user. The initial loading of the graphs out of the viewport is now being delayed until they become visible to the user. This is a performance improvement for views showing a lot of graphs.

6 years, 8 months

Check_MK Werk 5476: Fixed notification numbering of periodic notifications

by Sven Panne

ID: 5476 Title: Fixed notification numbering of periodic notifications Component: cmc Level: 2 Class: Bug fix Version: 1.5.0i3 Previously, non-OK state changes during periodic notifications resetted the notification number back to 1, in effect restarting escalations. This was inconsistent with Nagios and is not what one wants: If e.g. a service is in WARN state for quite some time, and then goes to CRIT, one surely wants to continue escalation, not reset it. This problem has been fixed, so problems correctly escalate now.

6 years, 9 months

Check_MK Werk 5267: cmk-update-agent: New binary format of Agent Updater executable on Linux

by Andreas Umbreit

ID: 5267 Title: cmk-update-agent: New binary format of Agent Updater executable on Linux Component: agents Level: 2 Class: New feature Version: 1.5.0i2 The cmk-update-agent executable is now implemented as a packaged binary executable. This werk consists of many changes that have partly already been applied to Check_MK 1.5.0i1. The new format addresses several problems and yields some improvements: * Better compatibility: All requirements regarding the installed Python Interpreter or other packages/programs were eliminated; the only requirements left are a x86_64 processor architecture and a glibc 2.5 or above. * More convenient communication to Check_MK Server: All GET-Requests have been replaced with according POST-Requests. This improves security as sensitive data is no longer sent within the URL of the HTTP(S) request. * Only one copy of cmk-update-agent: The copy of cmk-update-agent previously placed under /usr/bin/cmk-update-agent has been replaced by a shell script that executes the actual cmk-update-agent executable situated at the Check_MK Agent plugin directory. This eliminates the need to maintain two places when manually replacing cmk-update-agent for debugging reasons. However, it is still possible to execute a copy of the cmk-update-agent executable directly. * Notably, there will be no more problems with curl and because all communication is now done via python-requests, which is included within the cmk-update-agent executable as mentioned above.

6 years, 9 months

Check_MK Werk 5265: cmk-update-agent: Enable Agent Updater to update itself on Windows

by Andreas Umbreit

ID: 5265 Title: cmk-update-agent: Enable Agent Updater to update itself on Windows Component: agents Level: 2 Class: Bug fix Version: 1.5.0i2 When triggering an update under Windows, the agent updater could not be replaced by its new downloaded version because it was still running from the corresponding file. This situation is now mitigated by restarting the agent updater from within ../temp when running from plugins-dir. This is relevant only for a manual execution of cmk-update-agent.exe

6 years, 9 months

Check_MK Werk 5569: Graph layout is now more customizable

by Lars Michelsen

ID: 5569 Title: Graph layout is now more customizable Component: metrics Level: 2 Class: New feature Version: 1.5.0i2 The styling of the Check_MK graphs has now been unified for the most places where the graphs are rendered: <ul> <li>Regular graph dashlets</li> <li>Custom graph dashlets</li> <li>Graphs in views</li> <li>Graphs in reports</li> </ul> These standard render options are now available: <ul> <li>Font size</li> <li>Title (Show, show inline, hide)</li> <li>Add host/service information to title</li> <li>Show time range of graph (top right)</li> <li>Show margin round the graph</li> <li>Show graph legend</li> <li>Show vertical axis</li> <li>Show time axis</li> <li>Show graph controls</li> <li>Show pin</li> <li>Show previews</li> <li>Colors (Background, foreground, canvas)</li> </ul> Some of these options are specific for the medium they are rendered on. For example the graph controls are not available in graphs rendered in reports. These options are hidden from the configuration.

6 years, 9 months

Check_MK Werk 5567: Scheduled reports can now be stored in the site

by Lars Michelsen

ID: 5567 Title: Scheduled reports can now be stored in the site Component: Reporting & Availability Level: 2 Class: New feature Version: 1.5.0i2 Instead of sending an email with the created report in the scheduled interval it is now possible to store the just created reports locally in the site. This feature is configured in the configuration of the schedule. You can now choose the action Store locally instead of Send via Email and configure different action specific things after this. Each user allowed to use the report scheduler can open the page "Scheduler > Stored reports" to view and open all stored reports available to the user. All reports are stored below <tt>~/var/check_mk/reports/archive/</tt>. In the first directory below the base directory each user that creates such stored reports gets a directory. All stored reports of this user are saved below this directory. In case the user configures a schedule to publish the resulting PDFs to other users, the reports are stored in the <tt>public</tt> sub directory. A schedule can be configured to store the report either directly in these directories or in a hierarchy of subdirectories below these parent directories. You can configure stored reports to be deleted after a given time.

6 years, 9 months

Check_MK Werk 5524: Check API: Fix set_item_state/get_rate/get_counter logic when called from check functions

by Konstantin Büttner

ID: 5524 Title: Check API: Fix set_item_state/get_rate/get_counter logic when called from check functions Component: Checks & agents Level: 2 Class: Bug fix Version: 1.5.0i2 In the 1.5.0 branch, the logic encoding the current item in the key for saved data between checks was broken for checks with item and parse function. This did not affect the 1.4.0 branch.

6 years, 9 months

Check_MK Werk 5539: Improved performance of pages showing many graphs

by Lars Michelsen

ID: 5539 Title: Improved performance of pages showing many graphs Component: metrics Level: 2 Class: New feature Version: 1.5.0i2 Previously the GUI was loading all graphs in the progress of rendering a view. The view was rendered to the user once the information for all graphs is known. This mechanism made pages that show a lot of graphs load slowly. With this change the views are now rendered with a place holder for each graph which is a lot faster. After the view has been loaded for the user, the browser starts to render the graphs asynchronously and simultaneously which will also reduce the total time needed for loading.

6 years, 10 months

Check_MK Werk 5535: Check_MK hosts can now use multiple agents

by Lars Michelsen

ID: 5535 Title: Check_MK hosts can now use multiple agents Component: Core & setup Level: 2 Class: New feature Version: 1.5.0i2 It is now possible to configure multiple Check_MK agents for a single host. With this change, you can now configure e.g. a ESX VCenter to use the ESX special agent together with the regular Check_MK agent installed on the monitored host. All existing hosts remain using their existing configuration after an update. Also new hosts only use a single Check_MK agent using the already existing logic where a) The Check_MK agent was contacted via TCP or b) a configured data source program (special agent or other program invocation) was used. The new feature can be enabled by changing the host attribute (on hosts or folders) "Check_MK Agent" to e.g. "Contact Check_MK agent and all datasource programs". This will make Check_MK use all data sources matching on this host instead of just picking the first matching one. There is also an alternative option "Use all enabled datasources" available which can be used to execute only the data sources matching the host. On the way to this change we have changed server previously existing things: <ul> <li>The host tag group <tt>agent</tt> has been split into multiple tag groups to be more flexible.</li> <li>The tag group <tt>ping</tt> and <tt>snmp</tt> have been added and provide the options which were previously available in the single <tt>agent</tt> attribute.</li> <li>All these tag groups are treated as builtin tag groups defined by Check_MK (can not be modified anymore).</li> <li>Existing configurations of hosts/folders will be translated seamlessly into the new format.</li> <li>During updates your site will only apply the changes above in case you have an unmodified <tt>agent</tt> tag group. In case you have modified it in any way, these changes will not be applied and you won't be able to use the changes introduced with this werk. You will then have to clean up your local changes. Once you delete your local tag group "agent", the builtin one will be used automatically.</li> <li>The Edit host dialog has split up into more independent sections, the new ones are Address and Data sources to better visualize the relation of the different attributes.</li> </ul> Please note: In case you are using the Web-API calls to create or modify hosts or folders while setting attributes we changed with this change, you may have to change your API calls.

6 years, 10 months

Check_MK Werk 5532: Host/Service states and outputs can now be translated

by Lars Michelsen

ID: 5532 Title: Host/Service states and outputs can now be translated Component: cmc Level: 2 Class: New feature Version: 1.5.0i2 The states and service status detail of hosts and services can now be translated. You can now use the rules {{Host state translation}} and {{Service state translation}} to configure the Check_MK core to translate either specific states to other states or the status detail to other texts. States: For each host/service you can configure a transformation of each possible monitoring state to another one. The state translation can, for example, be used to inverse a host check in case you want to get a notification in case a host becomes reachable. The translation of detail outputs is done using regular expressions. You can specify multiple regular expressions (infix match, case sensitive) per object which are applied to the current status detail. The matched text will be replaced by the specified replacement text. You can use match groups to extract parts of the original text using the regular expression.

6 years, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2