Checkmk werks level1 August 2022

checkmk-werks-lvl1@lists.checkmk.com

25 participants
99 discussions

Checkmk Werk 14550: <tt>mk_logwatch</tt> via bakery: Add APPEND option for message classification

by Joerg Herbel

ID: 14550 Title: <tt>mk_logwatch</tt> via bakery: Add APPEND option for message classification Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 The <tt>mk_logwatch</tt> agent plugin can be deployed via the agent bakery (ruleset Text logfiles (Linux, Solaris, Windows)). In this ruleset, users can specify regular expressions for processing log messages. Before this werk, users could specify regular expressions to classify messages (OK/WARNING/CRITICAL), to ignore messages and to rewrite messages. As of this werk, users can additionally specify regular expressions to combine multiple log lines into a single message via the APPEND option, see the help of the bakery ruleset for details. One use case for this is the processing of multi-line stack traces. Note that this feature was already supported by the <tt>mk_logwatch</tt> agent plugin before this werk, but it was not configurable via the agent bakery.

1 year, 11 months

Checkmk Werk 14529: AWS special agent: improve performance for lambda functions data fetch

by Giordano Tomassorri

ID: 14529 Title: AWS special agent: improve performance for lambda functions data fetch Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 This werk improves the performances and reduces the number of API calls of the AWS special agent when fetching data for lambda functions. The change is mainly beneficial for users that are monitoring AWS accounts with several lambda functions that could hit a timeout before this change.

1 year, 11 months

Checkmk Werk 14167: Improved loading times of user configured graphs/views/dashboards/reports

by Andreas Boesl

ID: 14167 Title: Improved loading times of user configured graphs/views/dashboards/reports Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 Configurations with hundreds or thousands of custom visualization elements such as custom graphs suffered from slow page rendering, because the configuration files usually become quite large. To improve the loading time, an attempt is now always made to load a cached version of the file in question. The cached version is located in the tmpfs directory and also uses an optimized file format to reduce the parsing time by a factor of 10.

1 year, 11 months

Checkmk Werk 14148: Introduce column for details history

by Lukas Lengler

ID: 14148 Title: Introduce column for details history Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 When using the option "Write long output of services to monitoring history" the history can now be displayed as a column called "Details history".

1 year, 11 months

Checkmk Werk 14167: Improved loading times of user configured graphs/views/dashboards/reports

by Andreas Boesl

1 year, 11 months

Checkmk Werk 13731: HW/SW Inventory: Remove 'declare_invtable_view' for registration of table views

by Simon Jess

ID: 13731 Title: HW/SW Inventory: Remove 'declare_invtable_view' for registration of table views Component: HW/SW Inventory Level: 1 Class: New feature Version: 2.2.0i1 Previously a table in the HW/SW inventory tree could be opened as an own view if <ul> <li>the view name was added to the related display hint (with suffix {{_of_host}}) and</li> <li>the view was declared with {{declare_invtable_view}}.</li> </ul> The view declaration function {{declare_invtable_view}} was removed. Thus you also have to remove this function from your modules in order to avoid import errors. Moreover the view name does not have to end with {{_of_host}}. Example: C+: inventory_displayhints.update({ ... ".software.packages:": { "title": _l("Software packages"), "icon": "packages", "view": "invswpac_of_host", "keyorder": ["name", "version", "arch", "package_type", "summary"], }, ... } declare_invtable_view( "invswpac", # view name ".software.packages:", # legacy path _("Software package"), # title singular _("Software packages"), # title plural ) C-: Now only the view name in the related display hint has to be stated. C+: inventory_displayhints.update({ ... ".software.packages:": { "title": _l("Software packages"), "icon": "packages", "view": "invswpac", "keyorder": ["name", "version", "arch", "package_type", "summary"], }, ... } C-:

1 year, 11 months

Checkmk Werk 14682: Guard Livestatus against Nagios custom variables with an empty value.

by Sven Panne

ID: 14682 Title: Guard Livestatus against Nagios custom variables with an empty value. Component: Livestatus Level: 1 Class: Bug fix Version: 2.2.0i1 When Nagios is configured with custom variables having an empty value, various Livestatus queries can crash the Nagios core. This has been fixed. Reported by GitHub user ronansalmon, including a similar fix.

1 year, 11 months

Checkmk Werk 14691: pandacom_psu: Fix crash with missing PSU type

by Sofia Colakovic

ID: 14691 Title: pandacom_psu: Fix crash with missing PSU type Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Check pandacom_psu crashed during discovery for nmCarrierPSU1Type with values psu48VDC1100W (9) and psu230VAC1100W (10). The crash is now fixed and all existing PSU types are supported.

1 year, 11 months

Checkmk Werk 14065: azure_mysql: Monitor Azure database for MySQL

by Sofia Colakovic

ID: 14065 Title: azure_mysql: Monitor Azure database for MySQL Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 It's now possible to monitor Azure database for MySQL in Checkmk. Six new checks have been added: <ul> <li>Microsoft Azure MySQL Database: CPU Utilization</li> <li>Microsoft Azure MySQL Database: Connections</li> <li>Microsoft Azure MySQL Database: Memory Utilization</li> <li>Microsoft Azure MySQL Database: Network</li> <li>Microsoft Azure MySQL Database: Replication</li> <li>Microsoft Azure MySQL Database: Storage</li> </ul> The new services will be automatically discovered if you have an Azure database for MySQL in the resource group already monitored in Checkmk.

1 year, 11 months

Checkmk Werk 13915: Wait 30 s between failed attempts to connect to InfluxDB

by Mathias Laurin

ID: 13915 Title: Wait 30 s between failed attempts to connect to InfluxDB Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 After a failed attempt to connect to an InfluxDB server, the core now waits at least 30 s before trying again. This leads to, for example, an optimized DNS traffic. This delay of 30 s is not configurable by the end user.

1 year, 11 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 August 2022