Bug 1780408 - Add a simple set of usage metrics to understand workload configuration
Summary: Add a simple set of usage metrics to understand workload configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.3.0
Assignee: Clayton Coleman
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1780405
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-05 21:47 UTC by Clayton Coleman
Modified: 2020-01-23 11:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1780405
Environment:
Last Closed: 2020-01-23 11:17:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 582 0 'None' closed Bug 1780408: Gather ~10 metrics that tell us workloads that are being used 2020-03-10 10:05:14 UTC
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:18:08 UTC

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


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