Checkmk werks level1 July 2021

checkmk-werks-lvl1@lists.checkmk.com

22 participants
90 discussions

Checkmk Werk 12662: Fixed BI tree layouts "Table: bottom up" and "Table: top down"

by Andreas Boesl

ID: 12662 Title: Fixed BI tree layouts "Table: bottom up" and "Table: top down" Component: BI Level: 1 Class: Bug fix Version: 2.1.0i1

3 years, 1 month

Checkmk Werk 13064: proxmox_ve_vm_snapshot_age: new check to monitor the age of proxmox snapshots

by Maximilian Wirtz

ID: 13064 Title: proxmox_ve_vm_snapshot_age: new check to monitor the age of proxmox snapshots Component: Checks & agents Level: 1 Class: New feature Version: 2.1.0i1 Add a new check to monitor the age of Proxmox VE VM snapshots.

3 years, 1 month

Checkmk Werk 12845: Cleanup redundant custom sidebar snapin permission

by Lars Michelsen

ID: 12845 Title: Cleanup redundant custom sidebar snapin permission Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1 Previously there was a duplicate permission declared for each custom sidebar snapin. One permission was registered below the topic "Custom sidebar snapins" and one below "Snapins". The general permission from the "Snapins" section has now been removed for custom snapins.

3 years, 1 month

Checkmk Werk 12904: mrpe: Always display age of cached results

by Moritz Kiemer

ID: 12904 Title: mrpe: Always display age of cached results Component: Checks & agents Level: 1 Class: New feature Version: 2.1.0i1 The information about the age of cached agent data for mrpe based services is now always displayed in the same manner as for local check based services. Previously, users had to configure this with the `interval` option in the mrpe config file. This option has no effect anymore.

3 years, 1 month

Checkmk Werk 12987: Loss Of Absolute JVM Memory Levels During Update From 1.6 To 2.0

by Joerg Herbel

ID: 12987 Title: Loss Of Absolute JVM Memory Levels During Update From 1.6 To 2.0 Component: Setup Level: 1 Class: Bug fix Version: 2.1.0i1 In Checkmk 1.6, when creating rules of the ruleset "JVM memory levels", users have to choose between absolute or percentual memory levels. In Checkmk 2.0, users can create both absolute and percentual memory levels, independently of each other. During an update from 1.6 to 2.0, any user- defined absolute levels were lost. Percentual levels were not affected. This has been fixed.

3 years, 1 month

Checkmk Werk 12843: Fix GUI profiling not enabled immediately

by Lars Michelsen

ID: 12843 Title: Fix GUI profiling not enabled immediately Component: Multisite Level: 1 Class: Bug fix Version: 2.1.0i1 When the profiling of the GUI was enabled, the new global setting was not applied immediately. It was only effective for the second HTTP request to an apache process or after a reload or restart of the apache process. With this change, the setting is now applied immediately.

3 years, 1 month

Checkmk Werk 13086: Log error messages from the ICMP sender again.

by Sven Panne

ID: 13086 Title: Log error messages from the ICMP sender again. Component: cmc Level: 2 Class: Bug fix Version: 2.1.0i1 The CMC didn't pick up any error messages from the ICMP sender, which could in turn result in blocking the sender. This was a regression from 1.6.0.

3 years, 1 month

Checkmk Werk 12660: Improved data processing speed for BI availability computations

by Andreas Boesl

ID: 12660 Title: Improved data processing speed for BI availability computations Component: BI Level: 1 Class: New feature Version: 2.1.0i1 Transfering large amounts of data (>50MB) through the different Checkmk daemons took a considerable amount of time. Corrections were made in livestatus, liveproxyd and general data parsing. The mere data transfering/parsing part is now 20-30 times faster (80sec->3sec), herewith neglectible.

3 years, 1 month

Checkmk Werk 12389: HW/SW Inventory: Change raw tree structure

by Simon Jess

ID: 12389 Title: HW/SW Inventory: Change raw tree structure Component: HW/SW Inventory Level: 1 Class: New feature Version: 2.1.0i1 This only affects users which process raw trees from HW/SW Inventory system via <ul> <li>files {{var/check_mk/inventory/HOSTNAME}} or</li> <li>export hooks, similar to the ruleset {{Export List of Software packages as CSV file}} or</li> <li>(Web-)API, see also werk 3585.</li> </ul> Other functionalities like {{HW/SW Inventory History}} or using single values or tables from {{HW/SW Inventory}} trees in views are not affected. Old raw trees are migrated on-the-fly and the new structure is used. Summa summarum: If a user does not access raw trees from above topics then it seems that nothing has changed. Details: The previous raw tree structure of the {{HW/SW Inventory Tree}} had some disadvantages, ie. Python dicts or lists were used for two different entities: <ul> <li>single values or categories resp.</li> <li>tables or indexed categories</li> </ul> Example: A raw tree looked like: C:+ { "first-path-to": { "specific-single_values": { "single0": "Value 0", "single1": "Value 1", ... }, "single0": "Value 0", "single1": "Value 1", ... "table": [{"col0": "Value 0", "col1": "Value 1"}, ...], "category0": {...}, "category1": {...}, ... } "second-path-to": [ { "indexed0-specific-single_values": { "single0": "Value 0", "single1": "Value 1", ... }, "single0": "Value 0", "single1": "Value 1", ... "indexed0-table": [{"col0": "Value 0", "col1": "Value 1"}, ...], "indexed0-category0": {...}, "indexed0-category1": {...}, }, { "indexed1-specific-single_values": { "single0": "Value 0", "single1": "Value 1", ... }, "single0": "Value 0", "single1": "Value 1", ... "indexed1-table": [{"col0": "Value 0", "col1": "Value 1"}, ...], "indexed1-category0": {...}, "indexed1-category1": {...}, }, ... ], } C:- Moreover it was not clear and inflexible to which entity a path led: <ul> <li>path to single values or</li> <li>path to categories or</li> <li>path to tables or</li> <li>path to single values and categories or</li> <li>path to tables and categories or</li> <li>path to single values and tables or</li> <li>path to single values, tables and categories.</li> </ul> Example: It was impossible to have different entities below ["first-path-to", "table"]. The indexed categories are also cleaned up: there is no advantage of these list-based categories. Now the raw tree structure has basically the following form: C:+ { "Attributes": { "Pairs": {...}, }, "Table": { "Rows": [...], } "Nodes": { "path-to": { "Attributes": { "Pairs": {...}, }, "Table": { "Rows": [...], }, "Nodes": { "category": {...}, ... }, }, ... }, } C:- The main advantage of this new tree structure is that at every level each entity is encapsulated. Therefore single values ("Attributes"), a table ("Table") or categories ("Nodes") can "live" side-by-side. Beside other improvements like easier understanding of the raw tree structure the de/serializing process is less error-prone. Also the role of paths is clearer than before. Example: On a Linux machine with installed {{mk_inventory}} and 16000 entries the raw tree file increases from 347977 bytes to 349179 bytes, ie. 1202 bytes. The file size of small raw trees strikingly increase but for medium or large raw trees the file size does not increase as much (see above example).

3 years, 1 month

Checkmk Werk 13052: iis_app_pool_state: New check to monitor IIS Application Pool States

by Stefan Hölzl

ID: 13052 Title: iis_app_pool_state: New check to monitor IIS Application Pool States Component: Checks & agents Level: 1 Class: New feature Version: 2.1.0i1 New check to monitor each Application Pool State for an IIS. Discovers a service for each Application Pool.

3 years, 1 month

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 July 2021