Checkmk werks level1 December 2019

checkmk-werks-lvl1@lists.checkmk.com

13 participants
61 discussions

Checkmk Werk 10420: AWS EC2 Limits queries directly AWS Service Quotas for vCPU limits

by Óscar Nájera

ID: 10420 Title: AWS EC2 Limits queries directly AWS Service Quotas for vCPU limits Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 The AWS upgrade to vCPU-based instance limits is accompanied with a simplified overview of limits. However, this limits are regulated by customer's usage and change overtime to accompany growing demand. The AWS special agent now queries the AWS Service Quotas to update to your current limits to your different instance families.

4 years, 10 months

Checkmk Werk 10419: AWS EC2 Limits graphs collects now all instance types in a single graph

by Óscar Nájera

ID: 10419 Title: AWS EC2 Limits graphs collects now all instance types in a single graph Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 AWS EC2 Limits check plugin displayed in the service view one graph per running on-demand instance type. Now all instance types are collected in a single graph, where they are stacked. This allows for a simpler overview of running instances and the total amount running.

4 years, 10 months

Checkmk Werk 10418: Update AWS EC2 Limits to use new vCPU-based instance limits

by Óscar Nájera

ID: 10418 Title: Update AWS EC2 Limits to use new vCPU-based instance limits Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 Amazon EC2 transitioned from On-Demand instance limits from instance count-based limits to new vCPU-based limits. Checkmk now imitates that configuration and allows you to configure vCPU limits per EC2 instance family, in the same fashion as defined by AWS. In Checkmk count-based instance limits can still be used per instance type and total instances.

4 years, 10 months

Checkmk Werk 10417: AWS EC2 default limits are preserved for unconfigured instances

by Óscar Nájera

ID: 10417 Title: AWS EC2 default limits are preserved for unconfigured instances Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 AWS EC2 Limits check plugins had default values for the instance limits on each instance type. If user configures an specific instance with different limits, then all other instance defaults vanished. This werk recovers the check-plugin defaults for unconfigured instance type limits.

4 years, 10 months

Checkmk Werk 10654: hacmp_resources.py: allowing to save the any node option in the WATO configuration

by Wontek Hong

ID: 10654 Title: hacmp_resources.py: allowing to save the any node option in the WATO configuration Component: WATO Level: 1 Class: Bug fix Version: 1.7.0i1 The current version only allowed to save the "first node" option for the "Expect resource to be online on" rule configuration despite selecting the "any node" option. This new change now allows correct saving of the option.

4 years, 10 months

Checkmk Werk 10705: New "Tag usage" page to analyze tag references

by Lars Michelsen

ID: 10705 Title: New "Tag usage" page to analyze tag references Component: WATO Level: 1 Class: New feature Version: 1.7.0i1 A new subpage has been added to the tag management of WATO. This page can be used to analyze the usage of the different tags, for example to prepare cleanups or redesigns of tag schemes. This page can be used to get an idea of how the tags are used in hosts, folders and rulesets. The usage analyzation is currently not complete, it takes the same object types into account as the tag deletion / rename validation that is executed when making changes to tags. There are a lot of different objects that are using tags, which are currently not checked by WATO, for example: Rule based notifications, BI aggregations, status view filters and some more.

4 years, 10 months

Checkmk Werk 10701: Fix possible timeout exception during site update

by Lars Michelsen

ID: 10701 Title: Fix possible timeout exception during site update Component: Core & setup Level: 1 Class: Bug fix Version: 1.7.0i1 The Checkmk update command (cmk-update-config), which is executed during "omd update", could be terminated with a MKTimeout exception in previous 1.6 releases when updating larger configurations.

4 years, 10 months

Checkmk Werk 10650: job: Fixed wrong state marker

by Ronny Bruska

ID: 10650 Title: job: Fixed wrong state marker Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 If the service was in state WARN, the state marker for CRIT was shown. That has been fixed.

4 years, 10 months

Checkmk Werk 10649: ceph_status.pgs: Fixed Unknown service state for 'peering'

by Ronny Bruska

ID: 10649 Title: ceph_status.pgs: Fixed Unknown service state for 'peering' Component: Checks & agents Level: 1 Class: Bug fix Version: 1.7.0i1 If the device state was 'peering', the check went into UNKNOWN state. This has been fixed.

4 years, 10 months

Checkmk Werk 10648: jenkins_nodes: Added labels assigned to node

by Ronny Bruska

ID: 10648 Title: jenkins_nodes: Added labels assigned to node Component: Checks & agents Level: 1 Class: New feature Version: 1.7.0i1 In Jenkins, it is possible to define labels for each node. These labels are now shown in the service output of the check, if mode is "Exclusive". Furthermore, Checkmk discovers these labels now for it's own label mechanism.

4 years, 10 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Checkmk werks level1 December 2019