Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16031 discussions

Checkmk Werk 11078: Dynamic configuration: Add connector plugin API

by Lars Michelsen

ID: 11078 Title: Dynamic configuration: Add connector plugin API Component: DCD Level: 2 Class: New feature Version: 1.7.0i1 The Dynamic configuration is now loading plugins that are located below the path <tt>local/lib/check_mk/cee/dcd/plugins/connectors/</tt>. You can find a minimal example connector implementation it in your site at <tt>lib/check_mk/cee/dcd/plugins/connectors/example_connector.py</tt>. You may use this as base for your own connectors. To enable this connector, you need to copy it to the plugin directory mentioned above and uncomment the registry registration lines in the plugin (See TODO). To be able to configure connections based on this connector in the GUI, you also need to deploy a GUI plugin. An example can be found in your site at <tt>lib/check_mk/gui/cee/plugins/wato/example_dcd_connector.py</tt>. This needs to be placed in the WATO plugin directory of your site. You also need to uncomment the registry registration line in the plugin (See TODO).

4 years, 4 months

Checkmk Werk 11154: cisco_vpn_sessions: rename item "SVC" --> "AnyConnect SVC"

by Joerg Herbel

ID: 11154 Title: cisco_vpn_sessions: rename item "SVC" --> "AnyConnect SVC" Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 As a follow-up of werk #11152, this werk renames the item "SVC" of the check cisco_vpn_sessions to "AnyConnect SVC" (for clarity). Users have to re-discover the services of affected hosts for this to come into effect and potentially adjust any corresponding rules.

4 years, 4 months

Checkmk Werk 11078: Dynamic configuration: Add connector plugin API

by Lars Michelsen

4 years, 4 months

Checkmk Werk 11151: Correct handling of unsorted time periods for availability timelines

by Joerg Herbel

ID: 11151 Title: Correct handling of unsorted time periods for availability timelines Component: Livestatus Level: 1 Class: Bug fix Version: 1.7.0i1 Checkmk now handles unsorted time periods correctly when displaying availability timelines. For example, before, the time period 10:10 - 10:15, 10:00 - 10:05 would end up as 10:10 - 10:15, so checkmk dropped the second, earlier range.

4 years, 4 months

Checkmk Werk 10847: mk_oracle: Broken instance specific login in some cases

by Marcel Arentz

ID: 10847 Title: mk_oracle: Broken instance specific login in some cases Component: Checks & agents Level: 1 Class: Bug fix Version: 1.6.0p13 In some cases the SID as it is displayed on the host process list and the SID specific login data does not match if the matching is case sensitive. As a consequense the variable for the specific login has not been found, e.g. if the process is lower case but the config uses upper case SID.

4 years, 4 months

Checkmk Werk 11160: CSV/JSON/Python exports of views: improve formatting of labels

by Frans Fürst

ID: 11160 Title: CSV/JSON/Python exports of views: improve formatting of labels Component: Core & setup Level: 1 Class: Bug fix Version: 1.7.0i1 When exporting a view using %output_format=csv|json|python labels would not get exported properly (concatenated key/value pairs like "key1:value1key2:value2"). This fix turns the export for labels into raw data structures like {'key1':'value1', 'key2':'value2'}.

4 years, 4 months

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1