Hours-only graphs
NOTE: The feature branch for this was merged to 87-account-hours
to combine the work of both tickets
Summary
As a Cloud Meter customer, I want the overview graphs to show me the hours per day usage of RHEL and OCP so that I can easily understand my usage.
The intent here is to drop the rightmost combined graph and change the data displayed in the other two graphs to be the hours per day instead of instances seen per day.
Mockup: https://redhat.invisionapp.com/share/UFI078IZVAW#/screens/296433286
Acceptance Criteria
-
Verify the combined third/rightmost graph no longer exists. -
Verify the first/left graph displays the hours per day of RHEL. -
Verify the second/right graph displays the hours per day of OCP. -
Verify that the graphs are updated for the initial accounts list view. -
Verify that the graphs are updated for the secondary images list view. -
Verify that user-facing documentation exists and is updated to describe the expected behaviors of the graphs. -
Updated dashboard behavior concept info is here (The Cloud Meter dashboard and subsections until you get to flagging info): https://docs.google.com/document/d/1O2vBNGkP8zRLRzdrbWb9C8RpkBDFGpmbImuipmo7HcA/edit#heading=h.casn8q2useae
-
Assumptions and Questions
- This affects all of the current "graph" views. Including: the accounts summary and account details.
- This does not include the addition of select menus (as seen in the mockup) to change the graph contents to CPUs or memory. That will be defined in a later story.
- If there is no hourly usage data, we show zeros and a flat line.
- Since this implementation may not yet have the select menus, in their place we will simply include the text "Hours".
- The latest mockups include many additional changes to the look and feel of the pages that are not being included with this story in isolation. Effectively, we only care about the display of the graphs here.
- This design iteration of the graphs is what we believe to be valid for the foreseeable future. Now would probably be a good time to write user docs around the graphs — at least conceptually.
Edited by Calvin Spealman