Bug 1780408

Summary:	Add a simple set of usage metrics to understand workload configuration
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Monitoring	Assignee:	Clayton Coleman <ccoleman>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	alegrand, anpicker, erooth, juzhao, kakkoyun, lcosic, mloibl, pkrupa, surbania
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1780405	Environment:
Last Closed:	2020-01-23 11:17:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1780405
Bug Blocks:

Description Clayton Coleman 2019-12-05 21:47:42 UTC

+++ This bug was initially created as a clone of Bug #1780405 +++

In order to debug clusters, a high level understanding of the features and relative dimensions of usage is valuable for triage.  We should add a small set of metrics that gather relative usage (things like # of pods, # of workload controllers) to better triage clusters for services vs batch, density, and relative usage of development vs production features.

The set will be small and anonymous, and try to broadly characterize hot/dense, service vs batch, long running vs not, Openshift vs kube resources.

Comment 4 errata-xmlrpc 2020-01-23 11:17:47 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-2020:0062