Bug 1820254

Summary: charts do not accurately represent subscription limits
Product: Red Hat Hybrid Cloud Console (console.redhat.com) Reporter: Timothy Rees <trees>
Component: Subscription WatchAssignee: Kevin Howell <khowell>
Status: CLOSED CURRENTRELEASE QA Contact: Jon Allen <jallen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bclark, rjerrido, sghai
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-16 14:08:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
chart comparison none

Description Timothy Rees 2020-04-02 15:33:13 UTC 
Description of problem:

Subscription watch entitlement charts have excessive gradients (form over function?), without supplementary information this can give customers the impression that their subscription entitlements are allocated one by one over a period of time.  This is not the case, entitlement counts are reported once a day, chart should be stepped area to better represent this.  Example attached.

Version-Release number of selected component (if applicable):

N/A

How reproducible:

100%, every openshift customer is impacted

Steps to Reproduce:
1. Open subscription watch, look at chart; https://cloud.redhat.com/beta/subscriptions/openshift-sw
2.
3.

Actual results:

Chart shows gradients which span a number of hours, giving the impression that the number of entitlements gradually changes from one day to the next over the course of a few hours.

Expected results:

Number of entitlements is reported once per day, chart should be stepped area with very limited or no gradient from one day to the next if the number of entitlements change.

Additional info:

Exampled on the following googledoc; 
https://docs.google.com/spreadsheets/d/1yHHMV66bCVEDDOtopShwurnQnXszcZeGBJhQ0gvyVOU/edit?usp=sharing
Comment 1 Timothy Rees 2020-04-02 15:39:23 UTC 
Created attachment 1675804 [details]
chart comparison
Comment 2 bclark 2020-04-03 13:47:09 UTC 
The Subscription threshold is stepped because it really does change on a specific day.

Usage has easing because it is variable throughout the time period (day, week, etc). As Subscription Watch continues to evolve and add products, granularity, and stacked areas (similar to RHEL usage) to the app, this is the design capable of maintaining consistency.

The overall purpose of the graph is to easily see where your usage is compared to your subscription threshold. That being said, we understand the concern and are discussing ways to remove the potential confusion.
Comment 3 Rich Jerrido 2022-03-16 14:08:58 UTC 
We have made a number of changes to the graphs in Subscription Watch to address this issue (and a slew of others). Closing this BZ CURRENTRELEASE.