Bug 1733105 - Cloud provider type is not reported via metrics or telemetry, which prevents useful debug of clusters
Summary: Cloud provider type is not reported via metrics or telemetry, which prevents ...
Status: CLOSED DUPLICATE of bug 1732945
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-apiserver
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.z
Assignee: Lukasz Szaszkiewicz
QA Contact: Xingxing Xia
Depends On: 1731232
TreeView+ depends on / blocked
Reported: 2019-07-25 08:40 UTC by Michal Fojtik
Modified: 2019-07-30 07:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1731232
Last Closed: 2019-07-30 07:31:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-apiserver-operator pull 537 0 None closed Bug 1733105: Report infrastructure provider metric from the operator 2020-07-06 16:05:36 UTC

Description Michal Fojtik 2019-07-25 08:40:05 UTC
+++ This bug was initially created as a clone of Bug #1731232 +++

The core platform type is a key metric for debugging and triaging issues.  It is currently not available on cluster, nor reported via telemetry.

After discussion with apiserver team we will add

cluster_infrastructure_provider{type="AWS",region="us-east-1"} 1

cluster_infrastructure_provider{type="Azure",region=""} 1

cluster_infrastructure_provider{type="GCP",region="us-central"} 1

cluster_infrastructure_provider{type="OpenStack",region=""} 1

cluster_infrastructure_provider{type="BareMetal",region=""} 1

cluster_infrastructure_provider{type="",region=""} 1

reporting from the kube-apiserver and then add that telemetry, allowing cluster type to be unambiguously determined from metrics and alerting.

--- Additional comment from Clayton Coleman on 2019-07-18 17:27:51 UTC ---

Intended to be back ported to 4.1.

Comment 3 Lukasz Szaszkiewicz 2019-07-30 07:31:10 UTC

*** This bug has been marked as a duplicate of bug 1732945 ***

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