Checkmk werks level1 February 2023

checkmk-werks-lvl1@lists.checkmk.com

26 participants
104 discussions

Checkmk Werk 15236: Host renaming got stuck when "Automatically create monitoring agents" was activated

by Moritz Kiemer

ID: 15236 Title: Host renaming got stuck when "Automatically create monitoring agents" was activated Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 When the configuration option <i>"Automatically create monitoring agents"</i> was enabled, the operation <i>"rename host"</i> got stuck indefinitely. You can recover from this by killing the (second) apache processes accessing <tt>multisite.mk</tt> and restarting (CMC and apache): C+: OMD[mySite]:~$ fuser etc/check_mk/multisite.mk /opt/omd/sites/mySite/etc/check_mk/multisite.mk: 2294054 2294059 2294332 OMD[mySite]:~$ kill 2294059 OMD[mySite]:~$ omd restart C-:

1 year, 7 months

Checkmk Werk 15125: Fix cleanup of PDF tmp files in ~/tmp/check_mk

by Ronny Bruska

ID: 15125 Title: Fix cleanup of PDF tmp files in ~/tmp/check_mk Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 Created PDF tmp files were not cleaned up in folder ~/tmp/check_mk. Newly created PDF tmp files will be created in folder ~/tmp/check_mk/pdf and the new cronjob "cleanup_pdf_tmp_files", running every day at 00:15, will cleanup PDF tmp files older one day in this folder.

1 year, 7 months

Checkmk Werk 15146: azure_virtualmachines: Remove resource group from summary

by Sofia Colakovic

ID: 15146 Title: azure_virtualmachines: Remove resource group from summary Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 Previously, the resource group was shown in a summary of a VM service if VMs are maped to separate hosts (option 'Map data to the VM itself' in the agent config). With the werk 15261, the cmk/azure/resource_group:<group> label was added to all Azure hosts, which made this data redundant.

1 year, 7 months

Checkmk Werk 14794: Enable using Rulesets for section plugins

by Timotheus Bachinger

ID: 14794 Title: Enable using Rulesets for section plugins Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This werk is relevant for you if: <ul> <li> you implemented a host label function that is configurable via WATO <li> you do not have a discovery function that uses the same ruleset </ul> Previously, this was not possible. You may have encountered the following error: C+: Error running automation call restart (exit code 1), error: Invalid configuration variable 'YOUR_RULESET' --> Found 1 invalid variables If you use own helper variables, please prefix them with _. C-: Anyway - this is fixed now.

1 year, 7 months

Checkmk Werk 15219: time_period: disallow builtin timeperiod in timeperiod exclude

by Gav

ID: 15219 Title: time_period: disallow builtin timeperiod in timeperiod exclude Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 This werk fixes an issue where the user could via the REST-API select the builtin time period 24X7 as the timeperiod to exclude in a custom time period. This is no longer possible.

1 year, 7 months

Checkmk Werk 15272: juniper_fru: support for Juniper MX2010

by Benedikt Seidl

ID: 15272 Title: juniper_fru: support for Juniper MX2010 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1

1 year, 7 months

Checkmk Werk 14182: BI aggregations: Introduced option to freeze aggregation structure

by Andreas Boesl

ID: 14182 Title: BI aggregations: Introduced option to freeze aggregation structure Component: BI Level: 1 Class: New feature Version: 2.2.0i1 You can now choose to freeze the structure of an aggregation group. Once created, aggregations will never change their structure unless the user triggers a rebuild. To enable frozen aggregations, you have to set the new option <tt>New aggregations are frozen</tt> in the aggregation configuration page. If this option is set, all aggregation trees created from this aggregation are considered frozen right after their creation. It is still possible to re-freeze single trees of such an aggregation group. A snowflake icon has been introduced to indicate that an aggregation is frozen. If you click on this icon, an additional view will show the difference between the frozen aggregate and its live version. On this page you can also send a command to refreeze the frozen aggregation.

1 year, 7 months

Checkmk Werk 13972: Filters of 'list rulesets' endpoint have no effect

by Teresa Siegmantel

ID: 13972 Title: Filters of 'list rulesets' endpoint have no effect Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 Using various filters of the 'list rules' endpoint (GET '/domain-types/ruleset/collections/all') had no effect on the result. This is no longer the case. With this fix, the originally intended default behavior of the parameter such as 'used' and 'deprecated' are now respected and the endpoint returns only used rules unless specified otherwise.

1 year, 7 months

Checkmk Werk 15273: agent_azure: "No scheme supplied"

by Benedikt Seidl

ID: 15273 Title: agent_azure: "No scheme supplied" Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 Under certain circumstances agent_azure was exiting with the following error: C+: Invalid URL '': No scheme supplied. Perhaps you meant http://? C-:

1 year, 7 months

Checkmk Werk 15232: Re-evaluate active MKPs for minor version differences

by Moritz Kiemer

ID: 15232 Title: Re-evaluate active MKPs for minor version differences Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 This affects the newly introduced feature of having different MKPs active for remote sites with deviating Checkmk versions. Previously, we only re-evaluated the active MKPs for major version differences, but in fact we must do it whenever the remote sites version is not the same as the central sites version (as an MKP may only be applicable to a specific patch release).

1 year, 7 months

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 February 2023