Checkmk werks level1

checkmk-werks-lvl1@lists.checkmk.com

1 participants
16031 discussions

Checkmk Werk 7885: nfsiostat: Fix broken configuration

by Konstantin Büttner

ID: 7885 Title: nfsiostat: Fix broken configuration Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The ruleset intended for the nfsiostat plugin did not apply to the check. This has been fixed.

4 years, 5 months

Checkmk Werk 10933: Support STE2 for HWG Humdity and Temperature

by Timotheus Bachinger

ID: 10933 Title: Support STE2 for HWG Humdity and Temperature Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 STE *and* STE2 for HWG devices is now supported.

4 years, 5 months

Checkmk Werk 10934: sap_hana_status is now multiinstance compatible

by Timotheus Bachinger

ID: 10934 Title: sap_hana_status is now multiinstance compatible Component: Checks & agents Level: 2 Class: New feature Version: 1.7.0i1 The agent plugin mk_sap_hana already delivers data per SID. Now also the check sap_hana_status will generate a service for the status and version per SID. If you already discovered such services, rediscovery is needed.

4 years, 5 months

Checkmk Werk 11021: Fixed validation of regex filter

by Ronny Bruska

ID: 11021 Title: Fixed validation of regex filter Component: Multisite Level: 1 Class: Bug fix Version: 1.7.0i1 If you use invalid regex or lookaheads in views filter like "service", this could lead to timeouts and the possibility that you can not edit the view any more. Instead of that you will now get a message, that this input is not valid. If you already have configured such regex it is possible, that you have to adjust it.

4 years, 5 months

Checkmk Werk 10962: Bugfix for AWS monitoring (conversion Sum --> rates)

by Joerg Herbel

ID: 10962 Title: Bugfix for AWS monitoring (conversion Sum --> rates) Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 This werk fixes a bug which affected the conversion of AWS Cloudwatch metrics with a statistics of type "Sum" into rates. Without this fix, the computed rates are too high by a factor of 10. Affected checks: - aws_elb.http_elb - aws_elb.http_backend - aws_elb.backend_connection_errors - aws_elbv2_application.http_elb - aws_elbv2_application_target_groups_http - aws_elbv2_application_target_groups_lambda - aws_s3_requests - aws_s3_requests.http_errors Note that only the absolute values were affected, no the computed percentages (if any).

4 years, 5 months

Checkmk Werk 10961: Monitoring of AWS DynamoDB tables

by Joerg Herbel

ID: 10961 Title: Monitoring of AWS DynamoDB tables Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 This werk introduces monitoring of AWS DynamoDB tables. The monitoring includes overall limits for AWS DynamoDB (both account-wide and per-table limits on Read and Write Capacity Units) and a summary of all tables. Furthermore, we also monitor read and write capacities as well as latencies on a per-table basis. To make use of this werk, you have to configure the related AWS special agent to monitor Dynamo DB.

4 years, 5 months

Checkmk Werk 10962: Bugfix for AWS monitoring (conversion Sum --> rates)

by Joerg Herbel

4 years, 5 months

Checkmk Werk 11058: NagVis: Updated to 1.9.19

by Lars Michelsen

ID: 11058 Title: NagVis: Updated to 1.9.19 Component: Other Components Level: 1 Class: Bug fix Version: 1.7.0i1

4 years, 5 months

Checkmk Werk 10778: Cisco CPU checks: relax SNMP scan function

by Óscar Nájera

ID: 10778 Title: Cisco CPU checks: relax SNMP scan function Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 The Cisco CPU checks discovery ordering from Werk 7458 is revisited. There are four Cisco CPU checks: cisco_cpu, cisco_cpu_multiitem, cisco_nexus_cpu, cisco_oldcpu. We discover the Cisco CPU utilization services in the following order: - if it's a Nexus device the cisco_nexus_cpu check is used - if the device contains the SNMP table .1.3.6.1.4.1.9.9.109.1.1.1.1.2.* then cisco_cpu_multiitem is used - if the device either the OID .1.3.6.1.4.1.9.9.109.1.1.1.1.8.1 or .1.3.6.1.4.1.9.9.109.1.1.1.1.5.1 then cisco_cpu. This acts now as a fallback and is not strict about verifying device not belonging to cisco nexus family. This as a relaxed condition to werk 5748. - if .1.3.6.1.4.1.9.2.1.57.0 exists then cisco_oldcpu is used There may be Cisco hosts which have discovered the 'wrong' check type. After a re-discovery the CPU check type may change.

4 years, 6 months

Checkmk Werk 10601: Auto migration of check plugins to new section definitions

by Moritz Kiemer

ID: 10601 Title: Auto migration of check plugins to new section definitions Component: Checks & agents Level: 2 Class: New feature Version: 1.7.0i1 We are now converting all plugins to the new format expected by the future API. Migrated are plugins from <ul> <li>share/check_mk/checks</li> <li>local/share/check_mk/checks</li> <li>share/check_mk/inventory</li> <li>local/share/check_mk/inventory</li> </ul> Although we are trying to migrate as many check and inventory plugins as possible on the fly, for some plugins this may fail. These are the anticipated reasons why auto-migration may fail: <h4>A cluster aware checkplugin</h4> Checkmk refuses to auto-migrate cluster aware (those with node_info set to True) check plugins. Auto converting the data layout is too error prone. These plugins must be migrated manually. <h4>Checkplugins using 'extra_sections'</h4> Checkmk refuses to auto-migrate check plugins that make use of the 'extra_sections' feature. In the new API the destiction between the regular section and additional 'extra_sections' is not made, and all section content will be passed in its 'parsed' version. Therefore these Plugins have to be migrated manually. <h4>A missing SNMP scan function</h4> Every Checkplugin that specifies an 'snmp_info' key must specify 'snmp_scan_function' as well. <h4>A complex SNMP scan function</h4> If Checkmk fails to auto-migrate a legacy SNMP plugin to a section definition, this is most likely due to an elaborate scan function. For the auto-migration to work, the scan function must be fairly simple. Make sure your scan function has the following properties: <ul> <li>it only consists of one single return statement</li> <li>it does not in turn call other functions (not even 'all' or 'any')</li> <li>it does not negate compound expressions</li> </ul> If in doubt, take a look at scan functions that succeed to be migrated to see what options are available. <h4> Known limitations</h4> <ul> <li>HostLabels that are generated in a subchecks discovery function are lost</li> </ul>

4 years, 6 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1