Checkmk werks level1 May 2020

checkmk-werks-lvl1@lists.checkmk.com

14 participants
67 discussions

Checkmk Werk 11080: Port Checkmk to Python 3

by Lars Michelsen

ID: 11080 Title: Port Checkmk to Python 3 Component: Core & setup Level: 3 Class: New feature Version: 1.7.0i1 Most of Checkmk is written in Python. We have been developing on Python 2 for over 10 years now and are now taking the big step of porting Checkmk to Python 3 with Checkmk 1.7. This is a very big change in the software which has cost us a lot of time. But this step is necessary to continue to develop Checkmk efficiently and safely. In the past, Python 2.7 with all necessary 3rd party modules have been shipped in Checkmk for a long time. This Python 2.7 will no longer be shipped with Checkmk 1.7. Instead we now ship Python 3.8 with all necessary 3rd party modules. This is especially important if you use your own plugins or scripts. You have to consider the following things. If you have a script that is called directly from a cronjob or the core, e.g. a notification script, you have often used the shebang "#!/usr/bin/env python" in the past. By doing so, you have used the Python 2.7 that we shipped. Since this no longer exists, "python" of the operating system is used without further adaptation. This can be a Python 2.7, it depends on your system. We recommend changing the shebang to "#!/usr/bin/env python3". This will allow you to use the Python that comes with Checkmk again. After you have done this, you may need to adjust some things in your scripts to change your code from Python 2 to 3. We will publish more information about the conversion of plugins and scripts soon.

4 years, 4 months

Checkmk Werk 11107: mgmt_fsc_sc2_cpu_status: Typo in service description

by Moritz Kiemer

ID: 11107 Title: mgmt_fsc_sc2_cpu_status: Typo in service description Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 There was a typo in the service description of mgmt_fsc_sc2_cpu_status. It read "Inferface" instead of "Interface". The affected services need to be rediscovered.

4 years, 4 months

Checkmk Werk 11150: Refactoring of the monitoring of Cisco VPN sessions

by Joerg Herbel

ID: 11150 Title: Refactoring of the monitoring of Cisco VPN sessions Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 This werk refactors the code for monitoring the number of Cisco VPN sessions. The three checks cisco_asa_ipsecsessions, cisco_asa_svcsessions and cisco_asa_webvpnsessions are replaced with one check with three items (cisco_vpn_sessions). The corresponding rule for defining upper levels on the number of active sessions is renamed from "Cisco SVC/WebVPN/IPsec Sessions" to "Cisco VPN Sessions" This change is incompatible. Users have to re-discover the services of affected hosts and re-create the rules for the upper levels on the number of active sessions. Furthermore, any previously created rules should be deleted, since they are deprecated as of this werk and have no more effect.

4 years, 4 months

Checkmk Werk 11095: AWS S3

by Joerg Herbel

ID: 11095 Title: AWS S3 Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 This werk fixes multiple issues with the AWS S3 monitoring, i.e.: - As a follow-up for werk #11092, where one service per monitored region for the monitoring of AWS limits was introduced, the corresponding service for S3 is now always discovered as 'AWS/S3 Limits Global'. This is because there are no per-region limits for S3, only global account-wide limits. Users have to re-discover this service and potentially adjust any related rules for this to come into effect. - The regions set when configuring the AWS special are now properly taken into account when monitoring S3 buckets (note that they are deliberately ignored for the limits). This means that buckets residing in regions which are not monitored are not discovered any more and do not contribute to the S3 summary service. Users have to re-discover the S3 services for this to come into effect. - AWS S3 CloudWatch metrics are now fetched properly. Previously, only the non-request metrics for buckets in the region us-east-1 worked, such that for example bucket sizes for buckets outside us-east-1 were wrong. - A couple of metrics and some units were fixed. - The rule "AWS/S3 HTTP Errors" for the check aws_s3_requests.http_errors has been added. - The levels for the check aws_s3_requests.latency (rule "AWS/S3 Latency") are now specified in ms, before, the smallest possible level was 1 s. After installing the werk, users have to re-define this rule. - Rules configured for the check aws_s3_requests ("AWS/S3 Bucket Requests") now have an effect, previously, they were ignored. - Services based on S3 CloudWatch metrics now go stale instead of UNKN if AWS stops delivering data, for example in the case where requests to an S3 buckets stop. - Names and tags set when configuring the AWS special agent are now handled correctly and excluded buckets are not fetched any more (but they are still counted for the limits).

4 years, 4 months

Checkmk Werk 11094: AWS RDS

by Joerg Herbel

ID: 11094 Title: AWS RDS Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 This werk fixes several issues with the AWS RDS monitoring: - User-defined instance names crashed the AWS special agent if the instance did not exist. - The restriction of the monitored instances using tags did not work. - Monitoring two or more regions which contained instances with the same names resulted in duplicate service names. As a result, only the services corresponding to one of the monitored regions were displayed. This is fixed by changing the corresponding service items to contain both the instance name and the region, which makes them unique. For this fix to take effect, users have to re-discover the affected services. Note that this renaming results in a loss of historically recorded metrics. Furthermore, any user-defined rules for these services which use service items might have to be adjusted. The following services are affected by the change described in the last point above: aws_rds_summary.db_status, aws_rds, aws_rds.cpu_credits, aws_rds.network_io, aws_rds.bin_log_usage, aws_rds.transaction_logs_usage, aws_rds.replication_slot_usage, aws_rds.disk_io, aws_rds.connections, aws_rds.agent_jobs, aws_rds.replica_lag.

4 years, 4 months

Checkmk Werk 10694: Windows Agent is able to install plugins.cap with empty files

by Sergey Kipnis

ID: 10694 Title: Windows Agent is able to install plugins.cap with empty files Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Previously the installation of the plugins.cap file with zero size files was not possible. Now the problem has been fully solved. See the ticket CMK-4519.

4 years, 4 months

Checkmk Werk 11039: Kubernetes: new option to add a namespace prefix

by Tom Baerwinkel

ID: 11039 Title: Kubernetes: new option to add a namespace prefix Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 The special agent for Kubernetes now supports an option to add the namespace of namespaced objects as a prefix to the hostname in Checkmk. This makes it possible to distinguish objects with the same name in different namespaces. A pod inside the namespace "prod" with the name "redis" would then e.g. be added with the hostname "prod_pod_redis". You don't need to activate this option if you don't use namespaces in your cluster.

4 years, 4 months

Checkmk Werk 10989: checkpoint_packets: Fixed handling of missing ESP en-/decrypted packets

by Simon Jess

ID: 10989 Title: checkpoint_packets: Fixed handling of missing ESP en-/decrypted packets Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1

4 years, 4 months

Checkmk Werk 11106: winperf_processor.util: Crash in case of services disovered pre 1.6

by Moritz Kiemer

ID: 11106 Title: winperf_processor.util: Crash in case of services disovered pre 1.6 Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 Serives discovered in checkmk version pre 1.6 crashed upon a missing parameter default variable. This has been fixed.

4 years, 4 months

Checkmk Werk 11097: emc_datadomain_mtree: add configuration option

by Joerg Herbel

ID: 11097 Title: emc_datadomain_mtree: add configuration option Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 The check emc_datadomain_mtree, which monitors the state of EMC Data Domain MTrees, is now configurable via the rule "State of EMC Data Domain MTree". This rule allows the user to modify the mapping from MTree states to monitoring states.

4 years, 4 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 May 2020