Checkmk werks level1 May 2022

checkmk-werks-lvl1@lists.checkmk.com

28 participants
121 discussions

Checkmk Werk 13948: Switch BI check and agent to the REST API

by Philipp Siegmantel

ID: 13948 Title: Switch BI check and agent to the REST API Component: BI Level: 1 Class: New feature Version: 2.2.0i1 The BI active check and agent will now use the REST API to retrive data. This also means that cookie authentication mode in the active check is no longer supported. You can use the header mode (the new default) instead.

2 years, 3 months

Checkmk Werk 13943: Site Overview Tooltips now can cross dashlet boundaries

by Philipp Siegmantel

ID: 13943 Title: Site Overview Tooltips now can cross dashlet boundaries Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 Before, the tooltips of the site overview were bound to the parents dashlets bondaries. They now can extend beyond them.

2 years, 3 months

Checkmk Werk 13919: Mobile UI: Fix forms

by Kenneth Okoh

ID: 13919 Title: Mobile UI: Fix forms Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 The forms of the mobile UI did not work correctly anymore. Now, the "Results" button functions as a submit button again. The dropdowns are rendered correctly and all form information is applied to the results view.

2 years, 3 months

Checkmk Werk 13903: Introduce additional CSRF checks

by Maximilian Wirtz

ID: 13903 Title: Introduce additional CSRF checks Component: Setup Level: 1 Class: Security fix Version: 2.2.0i1 Previous to this Werk most data changing requests needed a transaction id. This mechanism was not used in all methods and in some cases the transaction id mechanism was not a good fit. So now a new CSRF token is introduced and checks are implemented in various locations. If you scripted the UI you need to parse the CSRF token from the HTML and send it with the Post requests.

2 years, 3 months

Checkmk Werk 14320: Fix KeyError on mknotifyd start after upgrade to 2.1.0

by Ronny Bruska

ID: 14320 Title: Fix KeyError on mknotifyd start after upgrade to 2.1.0 Component: Notifications Level: 1 Class: Bug fix Version: 2.2.0i1 If the notification spooler was used on a remote site, after upgrade to 2.1.0 the start of the mknotifyd could fail with the error "KeyError: 'encryption'".

2 years, 3 months

Checkmk Werk 14032: fix escaping in path parameters

by Max Linke

ID: 14032 Title: fix escaping in path parameters Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 Previously the REST API sent links containing characters (e.g. ':') which were not properly escaped. Using them directly without additional escaping could result in a HTTP 404 error. This is now fixed. No further action is neccessary.

2 years, 3 months

Checkmk Werk 14033: Correct ruleset links for special agents

by Max Linke

ID: 14033 Title: Correct ruleset links for special agents Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 Previously the REST API would report incorrect ruleset names for special agents, including wrong links to the rulesets. This has now been fixed. No further action necessary.

2 years, 3 months

Checkmk Werk 14339: Jira & Jenkins special agents: fix password store usage

by Anastasiya Liatsetskaya

ID: 14339 Title: Jira & Jenkins special agents: fix password store usage Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 The special agents for Jira and Jenkins offered the password store usage in the user interface, but did not properly retrieve passwords from the store if used.

2 years, 3 months

Checkmk Werk 13785: netapp_api_qtree_quota: some instances of Qtree services not discovered

by Lisa Pichler

ID: 13785 Title: netapp_api_qtree_quota: some instances of Qtree services not discovered Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 In the event that a quota with the same name exists both with the quota type "user" and "tree", the relevant Qtree instance could not be discovered. This has been fixed.

2 years, 3 months

Checkmk Werk 14319: Fix error on using folder in rule search

by Ronny Bruska

ID: 14319 Title: Fix error on using folder in rule search Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 If the option "Folder" was used in the rule search, submitting the search button lead to the error "The selected element 'None' is not longer available. Please select something else.".

2 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2022