Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
15974 discussions

Checkmk Werk 13812: KUBE kube_cpu use latest cpu usage value when no new data is available

by Wontek Hong

ID: 13812 Title: KUBE kube_cpu use latest cpu usage value when no new data is available Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The check returned a 0 cpu usage value when the Kubernetes special agent was polled too frequently. This werk fixes this behaviour and returns the last reported usage value for a time interval of 60 seconds if no new data is available from the agent. If the last reported value is older than 60 seconds than the usage value will be omitted.

2 years, 6 months

Checkmk Werk 12703: Drop experimental PySNMP backend

by Mathias Laurin

ID: 12703 Title: Drop experimental PySNMP backend Component: agents Level: 1 Class: Bug fix Version: 2.2.0i1 The experimental PySNMP is dropped because it did not perform as expected. The classic backend will be selected instead for people who have set PySNMP previously.

2 years, 6 months

Checkmk Werk 13094: Various ValueSpec-related API cleanups

by Sven Panne

ID: 13094 Title: Various ValueSpec-related API cleanups Component: Checks & agents Level: 2 Class: New feature Version: 2.2.0i1 Various changes have been done to <tt>ValueSpec</tt> and its subclasses, improving maintainability and robustness. If you don't write your own complicated <tt>ValueSpec</tt> subclasses and you don't have any self-written complicated check parameters, you are probably not affected. <ul> <li> <tt>ValueSpec</tt>'s constructor doesn't accept any random unspecifed keyword arguments anymore. It is better to raise an exception at the incorrect call site than silently accepting every typo. To fix any problems with this change, just remove the offending keyword arguments, they served no purpose after all. </li> <li> <tt>ValueSpec.canonical_value()</tt> is an abstract method now, otherwise we force lots of places to handle <tt>None</tt>. Previously quite a few things worked only more or less by accident. If you implement your own <tt>ValueSpec</tt> subclass, you have to implement that method now, unless an intermediate class already does it for you. </li> <li> <tt>DropdownChoice</tt> and <tt>CascadingDropdown</tt> don't have a <tt>no_preselect</tt> keyword argument anymore. It was redundant, because <tt>no_preselect_title</tt> is enough: If this keyword argument is not <tt>None</tt>, <tt>no_preselect=True</tt> is implied. Previously one could specify nonsensical combinations of those arguments. To fix any problems with this change, just drop the <tt>no_preselect</tt> keyword argument. </li> <li> <tt>Alternative</tt>, <tt>UploadOrPasteTextFile</tt>, <tt>TextOrRegExp</tt>, and <tt>CAorCAChain</tt> don't have a <tt>style</tt> keyword argument anymore. It didn't serve any purpose since Checkmk 2.0. Just remove it. </li> </ul>

2 years, 7 months

Checkmk Werk 13639: Fix displaying agent output on crash report page

by Lars Michelsen

ID: 13639 Title: Fix displaying agent output on crash report page Component: Multisite Level: 1 Class: Bug fix Version: 2.2.0i1 When the crash report page displayed a agent based check report, it displayed an error message "Internal error: Unsupported type <class 'bytes'>" in the "Agent output" box. The agent output can now be displayed again, even if it might not be 100% correct in case there are characters included in the agent output which can not be encoded in the default page encoding (UTF-8). This is OK, because the agent output there is only for informational purposes. Users that want to have the full and correct agent output can download the crash report archive and extract the agent_output file from it.

2 years, 7 months

Checkmk Werk 13084: Reintroduce housekeeping job before activation runs

by Christoph Rauch

ID: 13084 Title: Reintroduce housekeeping job before activation runs Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1 In previous versions, the activation housekeeping job was changed to a background-job running every minute because the run sometimes took longer than 2 minutes (a hard timeout). Due to race conditions this change led to errors (missing activations) in some cases. Only having it delete activations older than 1h however led to exhaustion of disk-space in some cases. This change reintroduces the previously dropped house-keeping run right before the activation is started, while keeping the periodically run house-keeping job to clean up afterwards.

2 years, 7 months

Checkmk Werk 12702: Improve performance of recurring downtimes

by Mathias Laurin

ID: 12702 Title: Improve performance of recurring downtimes Component: Core & setup Level: 1 Class: Bug fix Version: 2.2.0i1

2 years, 7 months

Checkmk Werk 13775: Windows license localisation

by Max Linke

ID: 13775 Title: Windows license localisation Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 Previously, the plugin was not able to deliver the license information in the case of Windows with non-English localization. With this release the problem has been solved and the plugin delivers the correct license information in all cases.

2 years, 7 months

Checkmk Werk 13700: Move configuration options for some undesired agent properties

by Moritz Kiemer

ID: 13700 Title: Move configuration options for some undesired agent properties Component: Checks & agents Level: 1 Class: Bug fix Version: 2.2.0i1 The following configuration options have been moved from "Status of the Checkmk services" to "Checkmk Agent". <ul> <li>State in case of wrong agent version</li> <li>State in case of restricted address missmatch</li> <li>State in case of available but not enabled TLS</li> </ul> Existing rules are migrated during cmk-update-config.

2 years, 7 months

Checkmk Werk 13698: Deprecate configuration variable 'agent_min_version'

by Moritz Kiemer

ID: 13698 Title: Deprecate configuration variable 'agent_min_version' Component: Checks & agents Level: 1 Class: New feature Version: 2.1.0b2 This Werk only affects users that used a <tt>.mk</tt> file to configure the variable <tt>agent_min_version</tt>. It has never been configurable via WATO. The configuration variable 'agent_min_version' does not have any effect anymore. Setting the variable to an integer other than 0 (the default) lead to a crash, setting it to a string lead to unreliable behaviour. If you want to check the version of the installed agent, please configure a rule in the ruleset "Checkmk Agent".

2 years, 7 months

Checkmk Werk 13699: Move ruleset "Check for correct version of Checkmk agent"

by Moritz Kiemer

ID: 13699 Title: Move ruleset "Check for correct version of Checkmk agent" Component: Checks & agents Level: 1 Class: New feature Version: 2.2.0i1 The functionality of the former ruleset "Check for correct version of Checkmk agent" is now included in the service ruleset "Checkmk Agent". Existing rules are migrated during update.

2 years, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1