Bug 1474511

Description of problem:

The CPU (MHz) and CPU Usage (%) values shown in the Normal Operating Ranges widget are not consistent with each other. Likewise for the Memory (MB) and Memory Usage (%) values. For example:

Normal Operating Ranges (over 30 days)
CPU 	  	 
Max 	271.48 MHz
High 	249.15 MHz
Average 132.34 MHz
Low 	15.54 MHz

CPU Usage 	  	 
Max 	Not Available
High 	5.86%
Average 3.18%
Low 	0.51%

Memory 	  	 
Max 	366.17 MB
High 	318.35 MB
Average 164.68 MB
Low 	11.01 MB

Memory Usage 	  	 
Max 	Not Available
High 	10.43%
Average 5.10%
Low 	0.00% 

The percentages do not match the corresponding MHz/MB values, e.g.,

High CPU / High CPU Usage = 249.15 / 0.0586 = 4251.71 MHz
Avg CPU / Avg CPU Usage = 132.34 / 0.0318 = 4161.64 MHz
Low CPU / Low CPU Usage = 15.54 / 0.0051 = 3047.06 MHz

The displayed values for avg / high (avg + std dev) / low (avg - std dev) use the following fields in metric_rollups:

CPU:		cpu_usagemhz_rate_average
CPU Usage:	min_max[:max_cpu_usage_rate]
Memory:		derived_memory_used
Memory Usage:	min_max[:max_mem_usage_absolute_average]

The CPU and Memory values are taken from daily averages, whereas CPU Usage and Memory Usage are taken from max usage values.

See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1452364
https://bugzilla.redhat.com/show_bug.cgi?id=1468634
https://bugzilla.redhat.com/show_bug.cgi?id=1469243

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

5.8.1.4

How reproducible:

100%

Steps to Reproduce:
1.) Capture several days' worth of C&U data for a VM
2.) View NOR data

Actual results:

CPU and Memory values don't match corresponding CPU Usage and Memory Usage values.

Expected results:

CPU and Memory values match corresponding CPU Usage and Memory Usage values.

Additional info: