Please go to the Data Browser and take screenshot of the raw metrics for both 7.0 and 6.7.  We can then determine if it is a data collection issue or a charting issue. I think you will see that the data is far better in 7.0. First set the time zonar to the last 1 hour to be consitent with what we will see in the VI Client. Dashboards – Configuration – Data Then in the center pane VMware – Virtual Machines – (VM Name) – Host – CPUs – Utilization The data will look like this. Also post a concurrent screenshot of that VM’s CPU utilization as shown in the VI Client.  [IMAGE] [IMAGE]
So after waiting for more than half a year for 7.0, it appears that it does not fix inaccurate metric representations.  Do you think the following CPU metrics depict an accurate picture?  vCenter CPU Utilization graph for a sample VM: [IMAGE]  vFoglight CPU Utilization graph for the exact same VM: [IMAGE]  I had another discussion open on this topic titled "CPU Ready Time metric off after upgrade from 6.7 to 6.8", but decided to open a new one because the title may have been misleading.  It is the same issue and has not been resolved now since 6.7.  Whatever they changed in 6.8 has made Foglight almost useless to me (unreliable at best) and I am not sure why I am even paying maintenance on it now that I have to validate everything against vCenter or ESXTOP.
Inaccurate representations of vCenter metrics in Foglight