Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15966 discussions

Checkmk Werk 14829: Monitoring of Elasticsearch indices: Rework grouping of individual indices

by Joerg Herbel

ID: 14829 Title: Monitoring of Elasticsearch indices: Rework grouping of individual indices Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Elasticsearch can be configured to automatically add a timestamp to index names, see <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/date-index-…" target="_blank">the documentation</a>. This results in index names such as my-index-2018.09.12, my-index-2018.09.13, my-index-2018.09.14 etc. In Checkmk, users will most likely not want to monitor such indices as individual services. Instead, users want to monitor a service called "my-index", which accumulates data accross the individual sub-indices. Before this werk, Checkmk identified matching indices by cutting off index names after the first "-". This is far too restrictive. For example, the indices "customer-a" and "customer-b" were accumulated into one combined index called "customer", which is most likely unwanted. Also, this grouping was not configurable. As of this werk, Checkmk no longer does any grouping by default. Instead, the grouping can now be configured via the discovery ruleset <i>Discovery of Elasticsearch indices</i>. See the help texts in the user interface for details regarding the configuration options. This werk is marked as incompatible because it will result in changed service configurations (new and vanished services) if the index names contain "-". Using the new discovery ruleset, users can however reproduce the old behaviour before this werk. This can be achieved by grouping indices according to the regular expression <tt>[^-]+</tt>.

1 year, 10 months

Checkmk Werk 14786: Add support for Cisco C9800-CL WLC

by External contributor

ID: 14786 Title: Add support for Cisco C9800-CL WLC Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1

1 year, 10 months

Checkmk Werk 12525: Improve label colors

by Kenneth Okoh

ID: 12525 Title: Improve label colors Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 For the violet <i>explicit</i> labels the label color was too dark in the dark theme and the font color too dark in the light theme. Both stylings are fixed.

1 year, 10 months

Checkmk Werk 14972: mk_oracle.ps1: Oracle SID not correctly set as connection property "TNS alias"

by Lisa Pichler

ID: 14972 Title: mk_oracle.ps1: Oracle SID not correctly set as connection property "TNS alias" Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The agent plugin for Oracle on Windows, "mk_oracle.ps1", is able to connect to multiple Oracle instances. If the plugin was configured to connect to these instances with a specific user, the Oracle SID was not included in the settings for TNS alias, which meant the plugin could not connect to the relevant instances. This has been fixed.

1 year, 10 months

Checkmk Werk 14880: kube_cronjob_status: remove exception raise when job has more than one pod

by Wontek Hong

ID: 14880 Title: kube_cronjob_status: remove exception raise when job has more than one pod Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Prior to this werk, the check kube_cronjob_status raised an error when the job had multiple pods. This werk removes this restriction but does not change the behaviour that only the latest pod is used to determine the status.

1 year, 10 months

Checkmk Werk 13963: REST API will no longer fail handling folders with the "bake agent package" attribute

by Philipp Siegmantel

ID: 13963 Title: REST API will no longer fail handling folders with the "bake agent package" attribute Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 The endpoints regarding folders would fail with a 500 status code if a folder had the "bake agent package" attribute set. This is no longer the case.

1 year, 10 months

Checkmk Werk 14900: Make "Customize views" options more understandable

by Ronny Bruska

ID: 14900 Title: Make "Customize views" options more understandable Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 This werk adjusts the menu entries in "Display" when viewing views. Until now it was not really visible to users if they edited views of other users (this needs the permission "Edit foreign views"). The menu entries, shown if you visit a view, were adjusted as follows: * "Clone builtin view" for builtin views * "Edit my view" for customized views of the current user * "Clone view" for views of other users (without permission "Edit foreign views") * "Edit view of user X" and "Clone view" for views of other users (with permission) The last mentioned example should give users the option to optional make a copy of the current view instead of editing the view of another user.

1 year, 10 months

Checkmk Werk 14828: Docker agent plugin: Handle race conditions caused by removed containers

by Joerg Herbel

ID: 14828 Title: Docker agent plugin: Handle race conditions caused by removed containers Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 As of this werk, the docker agent plugin handles the following two race conditions: LI: Removal of a container exactly at the time when the agent plugin attempts to query container statistics (CPU usage etc.). Before this werk, depending on the docker version, the plugin crashed with either <tt>requests.exceptions.JSONDecodeError</tt> or <tt>json.decoder.JSONDecodeError</tt>. LI: For old docker versions only (eg. 1.31): Removal of a container in between querying the list of containers on the target system and subsequently querying the individual containers. For newer docker versions, the agent plugin already handled this race condition before this werk. Note that users have to update the agent plugin on affected systems in order to benefit from this werk.

1 year, 10 months

Checkmk Werk 14634: cpu_load: Check plugin used to crash if the number of cpus was 0

by LukaRacic

ID: 14634 Title: cpu_load: Check plugin used to crash if the number of cpus was 0 Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The check plugin used to crash if the number of cpus was 0. Now, if that is the case, it assumed that the number of cpus is 1.

1 year, 10 months

Checkmk Werk 14853: Add auto deleted events to history

by Konstantin Baikov

ID: 14853 Title: Add auto deleted events to history Component: metrics Level: 1 Class: Bug fix Version: 2.2.0i1 Before this change if the number of events reached a limit (rule or global) they were deleted, but without an entry in history. Now the proper history is recorded

1 year, 10 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1