Checkmk werks level1 January 2024

checkmk-werks-lvl1@lists.checkmk.com

1 participants
231 discussions

[2.2.0] Checkmk Werk 15298 created: mk_oracle: restore compatibility with oracle 12c

by Checkmk werks level 1

Title: mk_oracle: restore compatibility with oracle 12c Class: fix Compatible: compat Component: agents Date: 1698138075 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p18 <a href="https://checkmk.com/werk/14839">Werk #14839</a> added the function <tt>listagg</tt> to one of our queries. Older versions of oracle database expect a <tt>WITHIN</tt> statement after the <tt>listagg</tt> function. This was added to assure compatibility with older databases.

8 months, 2 weeks

[2.2.0] Checkmk Werk 15297 created: mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin

by Checkmk werks level 1

Title: mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin Class: fix Compatible: incomp Component: agents Date: 1698137301 Edition: cre Knowledge: doc Level: 1 Version: 2.2.0p18 Changes made in <a href="https://checkmk.com/werk/14839">Werk #14839</a> where only applied to the linux agent plugin of mk_oracle. Now those changes are also applied to mk_oracle.ps1

8 months, 2 weeks

[2.2.0] Checkmk Werk 16164 created: veeam_cdp_jobs: Handle last sync time from the future

by Checkmk werks level 1

Title: veeam_cdp_jobs: Handle last sync time from the future Class: fix Compatible: compat Component: checks Date: 1703838299 Edition: cre Level: 1 Version: 2.2.0p18 Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: C+: raise ValueError("Cannot render negative timespan") C-: Now, the time since the last job run will be 0 for such cases.

8 months, 2 weeks

[2.3.0] Checkmk Werk 15298 created: mk_oracle: restore compatibility with oracle 12c

by Checkmk werks level 1

[//]: # (werk v2) # mk_oracle: restore compatibility with oracle 12c key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-10-24T09:01:15+00:00 level | 1 class | fix component | agents edition | cre <a href="https://checkmk.com/werk/14839">Werk #14839</a> added the function <tt>listagg</tt> to one of our queries. Older versions of oracle database expect a <tt>WITHIN</tt> statement after the <tt>listagg</tt> function. This was added to assure compatibility with older databases.

8 months, 2 weeks

[2.3.0] Checkmk Werk 15297 created: mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin

by Checkmk werks level 1

[//]: # (werk v2) # mk_oracle.ps1: port changes made in werk 14839 to windows agent plugin key | value ---------- | --- compatible | no version | 2.3.0b1 date | 2023-10-24T08:48:21+00:00 level | 1 class | fix component | agents edition | cre Changes made in <a href="https://checkmk.com/werk/14839">Werk #14839</a> where only applied to the linux agent plugin of mk_oracle. Now those changes are also applied to mk_oracle.ps1

8 months, 2 weeks

[2.3.0] Checkmk Werk 16164 created: veeam_cdp_jobs: Handle last sync time from the future

by Checkmk werks level 1

[//]: # (werk v2) # veeam_cdp_jobs: Handle last sync time from the future key | value ---------- | --- compatible | yes version | 2.3.0b1 date | 2023-12-29T08:24:59+00:00 level | 1 class | fix component | checks edition | cre Previously, the veeam_cdp_jobs would crash when receiving last sync time from the future with a message: ``` raise ValueError("Cannot render negative timespan") ``` Now, the time since the last job run will be 0 for such cases.

8 months, 2 weeks

[2.3.0] Checkmk Werk 16261 created: Split up rule "Mails in outgoing mail queue"

by Checkmk werks level 1

[//]: # (werk v2) # Split up rule "Mails in outgoing mail queue" key | value ---------- | --- date | 2023-12-25T17:11:32+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | no This affects all users that had rules for "Mails in outgoing mail queue" configured. To clean up inconsistencies that the new APIs no longer tolerate, we had to split the ruleset into two. We renamed "Mails in outgoing mail queue" to "Mails in outgoing mail queue (multiple queues)" and added a new ruleset "Mails in outgoing mail queue (single queue)". The required new rules are created automatically during upgrade, but we advise users to check if they have rules that are not needed anymore. The plugins using the new ruleset are * Barracuda SPAM Firewall: Active and Deferred Mail Queue Length (`barracuda_mailqueues`) * Nullmailer: Mailqueue Length (`nullmailer_mailq`) * qmail: Mailqueue Length (`qmail_stats`)

8 months, 2 weeks

[2.3.0] Checkmk Werk 16277 created: Split up rule "Main memory usage of simple devices"

by Checkmk werks level 1

[//]: # (werk v2) # Split up rule "Main memory usage of simple devices" key | value ---------- | --- date | 2023-12-23T14:52:41+00:00 version | 2.3.0b1 class | fix edition | cre component | checks level | 1 compatible | no This affects all users that had rules for "Main memory usage of simple devices" configured. To clean up inconsistencies that the new APIs no longer tolerate, we had to split the ruleset into two. We renamed "Main memory usage of simple devices" to "Main memory usage of simple devices with multiple services" and added a new ruleset "Main memory usage of simple devices with single services". The required new rules are created automatically during upgrade, but we advise users to check if they have rules that are not needed anymore. The plugins using the new ruleset are * Check Point Firewalls: Memory Usage (`checkpoint_memory`) * HPE Procurve Switches: Memory Usage (`hp_procurve_mem`) * UCD SNMP Daemon: Memory Check (`ucd_mem`)

8 months, 2 weeks

[2.3.0] Checkmk Werk 14943 created: Agent updater: allow automation user to login with password

by Checkmk werks level 1

[//]: # (werk v2) # Agent updater: allow automation user to login with password key | value ---------- | --- date | 2024-01-02T16:50:40+00:00 version | 2.3.0b1 class | fix edition | cee component | agents level | 1 compatible | yes Up to now, when using the agent updater CLI, you would have to use the `--password` (or `-P`) parameter to specify the password for a human user and the `--secret` (or `-S`) parameter to specify the secret for an automation user. This starts to be confusing with the interactive mode: in that case the program assumes that you are using a human user and will fail if the credentials that you enter are valid credentials for an automation user. On top of that, the error message is completely misleading. With this commit, we are changing the behavior of the agent updater so that an automation user credentials will work even if the secret is specified with the `--password` (or `-P`) param. This way the end user don't have to care about which param name is the right one to use: they can just specify the password, or the secret, with the `--password` param and it will work. This also allows the interactive mode to work with an automation user. This change is backward compatible, meaning that everything that used to work up until now, will keep working even after this.

8 months, 2 weeks

[2.2.0] Checkmk Werk 16166 created: ibm storwize: Fix missing data when monitoring nodes

by Checkmk werks level 1

Title: ibm storwize: Fix missing data when monitoring nodes Class: fix Compatible: compat Component: checks Date: 1704272720 Edition: cre Level: 1 Version: 2.2.0p18 lsnodestats command was used for monitoring nodes in IBM Storwize devices. Storwize devices don't have the lsnodestats command which led to missing data in ibm_svc_nodestats services. Now, the IBM SVC agent uses the lsnodestats if it's available and lsnodecanisterstats otherwise.

8 months, 2 weeks

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 January 2024