Bug 1614877 - CPU Utilization chart doesn't follow usual conventions for reporting memory usage
Summary: CPU Utilization chart doesn't follow usual conventions for reporting memory u...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-monitoring-integration
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-10 15:24 UTC by Martin Bukatovic
Modified: 2019-05-08 18:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-08 16:05:16 UTC
Embargoed:


Attachments (Terms of Use)
screenshot 1: CPU Utilization chart on Host dashboard (229.78 KB, image/png)
2018-08-10 15:43 UTC, Martin Bukatovic
no flags Details
screenshot 2: munin cpu utilization chart for the same machine and time range as screenshot 1 (43.44 KB, image/png)
2018-08-10 15:46 UTC, Martin Bukatovic
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1614857 0 unspecified CLOSED Memory Utilization chart doesn't follow usual conventions for reporting memory usage 2021-02-22 00:41:40 UTC

Internal Links: 1614857

Description Martin Bukatovic 2018-08-10 15:24:35 UTC
Description of problem
======================

CPU Utilization chart doesn't follow usual conventions for reporting
memory usage: stacked area graph[1] is not used to convey the data.

This makes this chart less convenient and harder to understand.

[1] https://datavizcatalogue.com/methods/stacked_area_graph.html

Version-Release number of selected component
============================================

tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch

Steps to Reproduce
==================

1. Instal RHGS WA using tendrl-ansible
2. Import Trusted storage pool with at least one volume
3. Let RHGS WA to monitor cluster for some time
4. Go to Host dashboard and check CPU Utilization chart there

Actual results
==============

The CPU Utilization chart reports 2 values, one for cpu cycles accounted for
userland (user) and the other for kernel (system) as 2 independent lines in
a chart.

This makes the chart harder to read. Eg. on screenshot 1, user cpu utilization
is about 70 % and system one is about 30 % - but it's not immediately visible
that the total cpu utilization is 100 %.

Expected results
================

The CPU Utilization panel uses stacked area graph.

Additional info
===============

Definition of stacked are graph:
https://datavizcatalogue.com/methods/stacked_area_graph.html

Comment 1 Martin Bukatovic 2018-08-10 15:36:19 UTC
See also: similar problem with Memory Utilization chart

Comment 2 Martin Bukatovic 2018-08-10 15:43:25 UTC
Created attachment 1475112 [details]
screenshot 1: CPU Utilization chart on Host dashboard

The workload which caused such load is described as a reproducer for BZ 1614486.

Comment 3 Martin Bukatovic 2018-08-10 15:46:36 UTC
Created attachment 1475113 [details]
screenshot 2: munin cpu utilization chart for the same machine and time range as screenshot 1

On the screenshot 2, it's possible to see how would stacked are graph look like
for the same data as shown in WA dashboard in screenshot 1.

Looking at the screenshot 2 (from munin), one can immediately see that the total
utilization is 100 %.

Comment 5 Ju Lim 2018-08-13 16:20:05 UTC
I too agree the memory and CPU "trend" charts should be stacked.  I don't recall the previous upstream issues on this, but I know there's lots of issues raised upstream how to do stacked charts in grafana and it not always working and depends on the grafana version and plug-in.

That being said, I don't believe we can stack if with line charts (as stacked area charts like in Munin), but it looks like we can do this with the stacked bar charts in grafana.  See http://docs.grafana-zabbix.org/guides/gettingstarted/ (do a find for "stacked bars" and it should be fairly straight forward to change this, and there might be some adjustments with regards to max data points to make it look better.)

Thoughts?

Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1614857.


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