Checkmk werks level2

checkmk-werks-lvl2@lists.checkmk.com

1 participants
1349 discussions

Check_MK Werk 5873: IPMI Management board

by Lars Michelsen

ID: 5873 Title: IPMI Management board Component: Core & setup Level: 2 Class: New feature Version: 1.5.0i4 The management board of hosts can now be configured to be monitored via IPMI as alternative to the previous SNMP monitoring. To configure the IPMI management board for a host, you need to edit the host configuration. Set the addresss of the management board, choose IPMI as management board protocol and specify the IPMI credentials. After this, you should be able to find new services named "Management interface: ..." using the service discovery. To make your configuration a bit less explicit, you can specify the IPMI protocol and credentials on folders instead of specifying it explicit for each host. Another option is to use the ruleset "Management board config" to configure the credentials. But you will have to set at least the protocol on host/folders and the management board address for each host.

6 years, 6 months

Check_MK Werk 5781: Check_MK Update Agent: Now automatically repairs missing agent plugins after a failed windows agent update

by Andreas Umbreit

ID: 5781 Title: Check_MK Update Agent: Now automatically repairs missing agent plugins after a failed windows agent update Component: agents Level: 2 Class: Bug fix Version: 1.5.0i3 On some occassions, the windows agent may loose its agent plugins during an msi update. This issue is still being investigated. In the meantime, the cmk-update-agent.exe is now able to detect a failed installation and tries to repair the missing plugin files. Keep in mind that this workaround is only available -after- the next agent update, so the initial rollout of this update may still fail, since it is done by an earlier version of the agent updater.

6 years, 7 months

Check_MK Werk 5781: Check_MK Update Agent: Now automatically repairs missing agent plugins after a failed windows agent update

by Andreas Umbreit

6 years, 7 months

Check_MK Werk 5732: BI aggregations are now customer aware

by Lars Michelsen

ID: 5732 Title: BI aggregations are now customer aware Component: WATO Level: 2 Class: New feature Version: 1.5.0i3 The configuration if the BI aggregations is now handled in a customer aware way by the Check_MK Managed Services Edition. You can now configure each aggregation to be associated with a customer, the provider or being globally available. The aggregations are assigned to the provider by default. In case you want to have an aggregation only be synchronized to a single customer, you can configure it in the aggregation properties. A customer only get's the BI packs and BI rules synchronized that are needed to handle the aggregations that are made available to this customer.

6 years, 7 months

Check_MK Werk 5671: Use RE2 regular expression engine for Livestatus queries.

by Sven Panne

ID: 5671 Title: Use RE2 regular expression engine for Livestatus queries. Component: Livestatus Level: 2 Class: New feature Version: 1.5.0i3 Livestatus offers various places where a regular expression can be used, e.g. in its "Filter:" header for GET queries. The previous implementation had various problems, which have all been fixed by switching to a new regular expression engine (RE2, see https://github.com/google/re2): <ul> <li>Unicode was not handled correctly: RE2 fully understands UTF-8, so this has been fixed.</li> <li>Unbounded memory usage during matching: This could lead to stack overflows and CMC/Nagios crashes when trying to match some classes of regular expressions on long inputs. RE2 guarantees that this won't happen, it either complains that a regular expression is too complicated (which is hard to provoke) or runs in constant memory afterwards.</li> <li>Exponential runtime: Some classes of regular expressions could lead to exponential runtime, blocking Livestatus threads and using CPU time for some millenia or more. RE2's runtime is linear in the size of the regular expression and the input, so this has been fixed, too.</li> </ul> As an additional bonus, most of the time RE2 is quite a bit faster than the previous implementation. RE2's regular expression syntax (https://github.com/google/re2/wiki/Syntax) is basically a superset of the previous POSIX extended regular expression syntax (http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag…), so you won't have to change your patterns. Note that one esoteric detail is different, though, namely the semantics of submatching (see https://swtch.com/~rsc/regexp/regexp2.html#posix). If you relied on this, you probably already had some problems, because almost every POSIX regex implementation out there was buggy in some way (see https://wiki.haskell.org/Regex_Posix#Results_and_Bugs).

6 years, 7 months

Check_MK Werk 5708: df: Fix incorrect values being reported on devices with btrfs

by Konstantin Büttner

ID: 5708 Title: df: Fix incorrect values being reported on devices with btrfs Component: Checks & agents Level: 2 Class: Bug fix Version: 1.5.0i3 This fixes a bug introduced with Werk #4806.

6 years, 7 months

Check_MK Werk 5556: check_bi_aggr: Active Check for BI is now able to use the password store

by Marcel Arentz

ID: 5556 Title: check_bi_aggr: Active Check for BI is now able to use the password store Component: Checks & agents Level: 2 Class: New feature Version: 1.5.0i3

6 years, 7 months

Check_MK Werk 5653: New report element: Add host report for multiple hosts

by Lars Michelsen

ID: 5653 Title: New report element: Add host report for multiple hosts Component: Reporting & Availability Level: 2 Class: New feature Version: 1.5.0i3 Using the new report element "Host report for multiple hosts" it is now possible to include reports in other reports to instanciate it multiple times. For example you can now create a top-level "ESX host" report that contains sub reports for each of your ESX servers. All you need to do is to create a report that contains all the report elements you want to see for a single ESX server. Either the whole report or at least the single elements in that report need to have the "single host context" configured. Then you need to create a top level report, add the element "Host report for multiple hosts" to this report and select the previously configured host specific report as child report. In that element you also need to configure the "Search filters" to match the hosts you want to create the child elements for. In the example above you need to configure e.g. the host tag filter to select the ESX hosts.

6 years, 8 months

Check_MK Werk 5634: Fixed slowing of CMC stop operation when SNMP checks are running

by Lars Michelsen

ID: 5634 Title: Fixed slowing of CMC stop operation when SNMP checks are running Component: Core & setup Level: 2 Class: Bug fix Version: 1.5.0i3 The Check_MK Microcore may need a long time for completing stop/restart of the process waiting for currently running operations to finish. One possible situation was that the Check_MK check helpers currently execute checks in form of SNMP queries. A common case is that the helpers wait for the response of a SNMP device which may take up to minutes, depending on the "SNMP timing settings". We have now changed the logic that these SNMP queries are terminated which leads to an immediately ending Check_MK check helper and also a faster ending Microcore process. This change is especially important for cluster setups that have a tight timeout configured for the stop operation of the OMD sites. With this change the failover situations should be handled a lot faster and more stable.

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level2