Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15970 discussions

Check_MK Werk 5488: veeam_jobs: Add support for new veeam API

by Tom Baerwinkel

ID: 5488 Title: veeam_jobs: Add support for new veeam API Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i3 The new veeam API only supports StartTimeLocal and StopTimeLocal. The old API using StartTime and StopTime is not supported anymore. This lead to the error that backup jobs using the new API were shown as "No complete backup". This change adds support for StartTimeLocal and StopTimeLocal while maintaining compatibility to the old API.

6 years, 8 months

Check_MK Werk 5633: It is now possible to sort by the perfometer column

by Lars Michelsen

ID: 5633 Title: It is now possible to sort by the perfometer column Component: Multisite Level: 1 Class: New feature Version: 1.5.0i3 The service list status views of Check_MK can now be sorted by the column "Perf-O-Meter". The sorting of the perfometers is sorted by these values: <ol> <li>First sort by the optional perfometer group or perfometer ID</li> <li>Second sort by the sort value of each perfometer</li> </ol> The Perfometer group / perfometer ID Each perfometer declaration can have an optional element <tt>sort_group</tt>. This element holds a string that can be used to group different perfometers (that visualize comparable values) together. In case no <tt>sort_group</tt> is defined, the internal ID of the perfometer definition is used. This means that all perfometers which are rendered by the same logical function are sorted together in a perfometer group. The sort value The sort value of a perfometer is calculated in different ways for each perfometer type based on the current metrics of this service. <ul> <li>Logarithmic: The single logarithmic value displayed by this perfometer is used</li> <li>Linear: The first segment of the displayed values is used</li> <li>Stacked: The sort value of the first stacked perfometer is used</li> <li>Dual: The maximum of both displayed value is used for sorting</li> <ul> The sorting only works for perfometers that are implemented as metric plugin (in <tt>plugins/metrics/</tt>). The legacy perfometers that are implemented as perfometer plugins can not be sorted. Dear check developers: All perfometers that visualize equal types of values have to be sorted together in a sort group. For example all checks that monitor fileystems should have equal perfometers that can be compared to each other and should therefor be sortable by their disk usage.

6 years, 8 months

Check_MK Werk 5632: Fixed XSS when rendering values of dropdown choices

by Lars Michelsen

ID: 5632 Title: Fixed XSS when rendering values of dropdown choices Component: Multisite Level: 1 Class: Security fix Version: 1.5.0i3 When using the WATO configuration it was possible to create e.g. a service level definition with javascript code in it's alias. When this definition was configured in a rule of the ruleset "Service Level of Hosts", the javascript code could be executed in the browsers context of the user viewing the rule. The insertion of the javascript code is only possible for authenticated users with the permission to configure Check_MK.

6 years, 8 months

Check_MK Werk 5477: Rule-based recurring downtimes can have and end now.

by Sven Panne

ID: 5477 Title: Rule-based recurring downtimes can have and end now. Component: Core & setup Level: 1 Class: New feature Version: 1.5.0i3 Prevously, you could only specify a point in time when a rule-based recurring downtime starts. You can now optionally specify an additional point in time when no new downtimes will be started for such a rule, i.e. effectively disabling that rule from that point onwards. Note that specifying such an end point is not possible for ad-hoc downtimes, i.e. the ones entered directly without rules. This is caused by the underlying Nagios-compatible external commands which don't know such a field. Simply extending the commands by adding such a field is not a reliable option: In multi-site environments you can have a mix of monitoring cores and don't know which site uses which core.

6 years, 8 months

Check_MK Werk 5630: Host/Service detail views: Display notification related painters together at end of runtime data painters

by Lars Michelsen

ID: 5630 Title: Host/Service detail views: Display notification related painters together at end of runtime data painters Component: Multisite Level: 1 Class: New feature Version: 1.5.0i3

6 years, 8 months

Check_MK Werk 5631: New host/service painter to display the notification postponement reason of the Microcore

by Lars Michelsen

ID: 5631 Title: New host/service painter to display the notification postponement reason of the Microcore Component: Multisite Level: 1 Class: New feature Version: 1.5.0i3 The Check_MK Microcore has a mechanic that delays notifications for different reasons. For example service notifications are delayed when the service is in downtime or when the host of the service is down. With the new painters "Notification postponement reason" Check_MK is now showing the reason why a pending notification for a host/service is not yet sent to the user. This painter has been added to the host and service detail pages by default. The users could already check the notification logic and see the current postponement reasons using the cmc.log, but this needs command line access and is not very comfortable when having a larger installation which produces a lot of log entries.

6 years, 8 months

Check_MK Werk 5323: Notification mail: Added variables which will be replaced by the entities choosen below 'Create separate notification bulks based on'

by Simon Betz

ID: 5323 Title: Notification mail: Added variables which will be replaced by the entities choosen below 'Create separate notification bulks based on' Component: Notifications Level: 1 Class: New feature Version: 1.5.0i1 If bulking is enabled in notification mail the following variables will be replaced if the related entity is choosen below Create separate notification bulks based on. These are <ul> <li>Folder: <code>$FOLDER$</code></li> <li>Hostname: <code>$HOSTNAME$</code></li> <li>Service description: <code>$SERVICEDESC$</code></li> <li>Service level: <code>$SERVICE_LEVEL$</code></li> <li>Check type: <code>$CHECKCOMMAND$</code></li> <li>Host/Service state: <code>$STATE$</code></li> <li>Event console contact: <code>$EC_CONTACT$</code></li> </ul>

6 years, 8 months

Check_MK Werk 5269: cmk-update-agent: New show-config mode

by Andreas Umbreit

ID: 5269 Title: cmk-update-agent: New show-config mode Component: agents Level: 2 Class: New feature Version: 1.5.0i3 With this werk, a new debugging-feature gets added to the cmk-update-agent(.exe) executable. You can now display the current configuration and state saved within the cmk-update-agent.cfg and cmk-update-agent.state files. Please note that the configuration file is prioritized over the state file and only effective configurations will be shown. E.g. a saved Check_MK server from state file will be shadowed by a configured server from cfg file and hence it will not be shown by the show-config mode. You can invoke the show-config mode by running "cmk-update-agent(.exe) show-config"

6 years, 8 months

Check_MK Werk 5487: isc_dhcpd: Resolve performance issues

by Tom Baerwinkel

ID: 5487 Title: isc_dhcpd: Resolve performance issues Component: Checks & agents Level: 1 Class: Bug fix Version: 1.5.0i3 Resolves performance issues which could lead to a timeout when a large amount of pools and leases were present.

6 years, 8 months

Check_MK Werk 5628: Reduced default vertical axis width to previous width

by Lars Michelsen

ID: 5628 Title: Reduced default vertical axis width to previous width Component: metrics Level: 1 Class: Bug fix Version: 1.5.0i3 In 1.5.0i2 the vertical axis width was increased a bit by accident. This has now been reduced again to the intended width

6 years, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1