Bug 1749451 - [4.2]Clusters must report a metric that includes number of cores separated by node-role label, os arch, os type, and os version
Summary: [4.2]Clusters must report a metric that includes number of cores separated by...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Chris Hambridge
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks: 1750283 1755757
TreeView+ depends on / blocked
 
Reported: 2019-09-05 16:04 UTC by Clayton Coleman
Modified: 2019-10-16 06:40 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1750283 1755757 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:40:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubernetes kube-state-metrics pull 877 0 'None' 'closed' 'store: add kube_node_role metric' 2019-11-21 20:19:48 UTC
Github observatorium configuration pull 70 0 'None' 'closed' 'Bug 1749451: Add node_role_os_version_machine:cpu_capacity_cores:sum' 2019-11-21 20:19:48 UTC
Github openshift cluster-monitoring-operator pull 466 0 'None' 'closed' 'Bug 1749451: Capture sum of cpu capacity cores by OS (RHCOS or RHEL) with version, arch, and role for the nodes.' 2019-11-21 20:24:39 UTC
Github openshift cluster-monitoring-operator pull 478 0 'None' 'closed' 'Bug 1749451: Bump telemeter-client' 2019-11-21 20:19:48 UTC
Github openshift kube-state-metrics pull 16 0 'None' 'closed' 'store: add kube_node_role metric' 2019-11-21 20:19:49 UTC
Github openshift telemeter pull 235 0 'None' 'closed' ' Bug 1749451: Capture sum of cpu capacity cores by OS (RHCOS or RHEL), arch, and role for the nodes. ' 2019-11-21 20:19:49 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:44 UTC

Description Clayton Coleman 2019-09-05 16:04:39 UTC
In order to properly account subscription info, clusters must have a recording rule that captures the following data and reports it via telemetry, from 4.1 onwards.

Clusters must report a metric that includes number of cores summed across nodes, subdivided by node-role label (e.g. master, infra, etc), os arch (kube label), os type (rhcos / rhel / other), and os version (7, 8, etc).

This then must be back ported to 4.1.

Comment 10 Chris Hambridge 2019-09-19 09:35:33 UTC
The os_version label that was initially intended to be exposed was dropped with the following PR:
https://github.com/openshift/machine-config-operator/pull/657

The following issue is a replacement to provide the OS major version in the future:
https://github.com/openshift/machine-config-operator/issues/582

For the time being we are deferring the version until the above issue is implemented as it is not necessary for the subscription related metric we need. When the above OS major version label is added this metric may be updated, but it was decided not to pull in the os_image string to reduce parsing issues.

More context of this discussion can be found here:
https://github.com/openshift/cluster-monitoring-operator/pull/466#issuecomment-530094389

Comment 11 Frederic Branczyk 2019-09-23 08:11:52 UTC
Note that for 4.1 backporting, we are waiting for a bugzilla to reference here: https://github.com/openshift/kube-state-metrics/pull/17. If there is no bugzilla in verified we cannot go ahead with 4.1. If that's ok and expected, then feel free to ignore this comment, I just want to ensure there is no cyclic dependency of people waiting on each other :) .

Comment 12 Chris Hambridge 2019-09-25 14:34:43 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1749451#c10

Comment 14 Junqi Zhao 2019-09-26 08:08:27 UTC
Based on Comment 8 and Comment 10, move it to VERIFIED

Comment 15 errata-xmlrpc 2019-10-16 06:40:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922


Note You need to log in before you can comment on or make changes to this bug.