Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15966 discussions

Checkmk Werk 14826: <tt>check_http</tt>: Make method <tt>CONNECT:POST</tt> selectable in Checkmk user interface

by External contributor

ID: 14826 Title: <tt>check_http</tt>: Make method <tt>CONNECT:POST</tt> selectable in Checkmk user interface Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 The active check <tt>check_http</tt> is configurable in the Checkmk user interface via the ruleset <i>Check HTTP service</i>. As of this werk, this ruleset allows for selecting <tt>CONNECT:POST</tt> as HTTP method (relevant for connecting through a proxy server).

1 year, 11 months

Checkmk Werk 14852: Fix line number filter in event history

by Konstantin Baikov

ID: 14852 Title: Fix line number filter in event history Component: Event Console Level: 1 Class: Bug fix Version: 2.2.0i1 The Event history details are now displayed correctly for the selected event. Previously in some cases the history_line filter would not work correctly and the UI would show an error message like: "400: Timeout while waiting for free Livestatus channel"

1 year, 11 months

Checkmk Werk 14839: oracle_dataguard_stats: Bufix for wrong Recovery Status on RAC Standby

by External contributor

ID: 14839 Title: oracle_dataguard_stats: Bufix for wrong Recovery Status on RAC Standby Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The check results in false CRITs on RAC standby databases with multiple running instances. Some more changes are done, due to wrong design in old code. The option to monitor the MRP process has been removed, because it is not needed. The apply_lag is more important than the recovery process itself. If recovery has been stopped, the monitoring of apply_lag will lead to WARN/CRIT, which is the most important metric in a Data-Guard environment. BREAKING Change: The option mrp state has been removed, because it is not needed. A missing recovery process (MRP0) is not an issue, until the apply_lag has a proper WARN/CRIT definition - that is more important than a stopped recovery in the standby database.

1 year, 11 months

Checkmk Werk 14816: Enhance detection of postfix installation

by External contributor

ID: 14816 Title: Enhance detection of postfix installation Component: agents Level: 1 Class: New feature Version: 2.2.0i1 We now can detect the PID of a running postgres instance if it is not installed in `/var/spool/postfix`. To do this we search for the pid file in the queue directory as reported by `postconf`. You can find the new instances after updating the check mk agent.

1 year, 11 months

Checkmk Werk 14654: Host diagnose: Internal error: dictionary changed size during iteration

by Moritz Kiemer

ID: 14654 Title: Host diagnose: Internal error: dictionary changed size during iteration Component: Setup Level: 1 Class: Bug fix Version: 2.2.0i1 This fixes a regression introduced in Checkmk 2.1.0p15. If users try to change the host properties from the <i>"Test connection to <HOST>"</i> page, the above error was raised.

1 year, 11 months

Checkmk Werk 14172: BI: Fixed broken host_search/child-with filtering

by Andreas Boesl

ID: 14172 Title: BI: Fixed broken host_search/child-with filtering Component: BI Level: 1 Class: Bug fix Version: 2.2.0i1 The host search option "The found hosts' (with child filtering)" was broken since the BI rework 2 years ago. Any attempt to save this setting lead to an exception. The fix for this problem required a small change in the API specification for the <tt>refer_to</tt> field <ul> <li>"refer_to": "host" -> "refer_to": {"type": "host"}</li> <li>"refer_to": "child" -> "refer_to": {"type": "child"}</li> <li>"refer_to": "parent" -> "refer_to": {"type": "parent"}</li> <li>"refer_to": {was broken} -> "refer_to": {"type": "child_with", "conditions": {..}}</li> </ul>

1 year, 11 months

Checkmk Werk 14890: Fix possible error on filtering service level of hosts

by Ronny Bruska

ID: 14890 Title: Fix possible error on filtering service level of hosts Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 Using the filter "Host service level" for views with hosts with configured custom attributes could lead to an error message like "Internal error: invalid literal for int() with base 10".

1 year, 11 months

Checkmk Werk 14563: <tt>heartbeat_rscstatus<\tt>: Fix error during update

by External contributor

ID: 14563 Title: <tt>heartbeat_rscstatus<\tt>: Fix error during update Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 During discovery the plugin <tt>heartbeat_rscstatus<\tt> stores its discovery state. Updating Checkmk from 2.0.0 to 2.1.0 or updates within those versions would cause these states to be lost. This is indicated by following error message: C+: -| 8/27 Rewriting autochecks... -| Transform failed: host='host', plugin='heartbeat_rscstatus', ruleset='heartbeat_rscstatus', params={'discovered_state': 'none'}, error=AssertionError('non-empty params vanished') C-: With this werk, the states are correctly persisted.

1 year, 11 months

Checkmk Werk 14300: Make appliance snapin compatible with Checkmk Appliance firmware 1.6+

by Lars Michelsen

ID: 14300 Title: Make appliance snapin compatible with Checkmk Appliance firmware 1.6+ Component: Multisite Level: 1 Class: New feature Version: 2.2.0i1 When Checkmk is used on on the Checkmk Appliance 1.6 or newer, it is necessary to update the appliance sidebar snapin. Previous Checkmk versions displayed the error message 'Failed to render navigation: Traceback (most recent call last): File: "[stdin]", line 2, in <module> IOError: [Errno 2] No such file or directory' in the sidebar snapin. Background: The Checkmk Appliance firmware 1.6 migrates the internal software stack to Python 3.7 which makes it incompatible with the previous snapin. This change makes it possible to use Checkmk on older and newer appliance firmware.

1 year, 11 months

Checkmk Werk 14901: user_config: REST API fix to ensure the request and response schemas align

by Gav

ID: 14901 Title: user_config: REST API fix to ensure the request and response schemas align Component: REST API Level: 1 Class: Bug fix Version: 2.2.0i1 This werk introduces a fix that aligns both the response and request schemas on the user_config endpoints. The response schema now nests the enforce_password_change attribute just like the request schemas. So the response from a GET request has the same format as what is required in a POST/PUT request. Client scripts should be adjusted accordingly.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1