@badhikar Can you pls take a look?

Utilization card reports the actual utilization of storage(non-replicated, actual storage should be 3 x value + staticUsage) . It's the non-replicated storage, whereas the main dashboard shows the exact raw capacity used of the system. 
One of the reasons we cannot show the logical capacity(non-replicated) in the main Overview(ODF) dashboard is that the total logical capacity is dependent on various factors such as number of pools and their replica counts which can change the total capacity of the system all the time. 
This is a technical limitation and I see no workarounds at this point.

I have sent the findings of the bug on an email thread.

Send a PR: https://github.com/red-hat-storage/ocs-operator/pull/1433, in OCS-Operator.
This PR will reduce the collection interval of that particular rule group, so that the metrics collected will be more granular.

Moving it to ocs as it is fixed there.

Not a 4.10 blocker, moving it out.

Arun, PTAL.

Pointing out some general observations,

ODF Overview page graphs (IOPS, Throughput and Latency) shows the sum of Read+Writes of I/O when compared with the separate Read and Write graphs in StorageSystem's -> Overview Block & File page. So both set of graphs won't have a one to one correlation.

For,
IOPS
      ODF Overview page and StorageSystem Overview page has different time intervals.

Throughput
      Underlying queries are different with different collection interval.

Latency
     Again two totally different queries (where one taking an average and the other taking sum).

For IOPS we can correct the time interval and make it same and for the other two need to check/investigate a bit further on the queries.

PR submitted to both ODF-Console and OCS-Operator repos

https://github.com/red-hat-storage/ocs-operator/pull/1761
https://github.com/red-hat-storage/odf-console/pull/352

Using version 4.12.0-114: IOPS, Throughput, Latency from Performance card and Used Capacity value from System Capacity are very closed to each other.