At first in the beginning the EWA report only reported the standard CPU data for the physical server and the data for this is directly collected by SAPOSCOL in a 24 hour buffer in which for each hour 4 times 60 measurements are stored because SAPOSCOL collects the data every 15 seconds by default.
After this SAP decided to create new monitor structures for the OS virtualization but the monitoring data for the CPU_Virtualization_Power
is not stored in the 24 hour SAPOSCOL buffer anymore. Actually the data is still collected by SAPOSCOL but only as a snapshot and we do need the
CCMS monitoring segment to store the data for a longer period. This can be done by using an ABAP report which reads the SAPOSCOL snapshot
data and stores the data in the CCMS monitor segment but this report only can be started each 5 minutes or this can be done by using a SAPCCM4X
agent and the agent can read the SAPOSCOL snapshot data every 60 seconds and sometimes even a little bit faster than this.
Now, if you do not use the SAPCCM4X agent then the difference between the old EWA report and the new one is 240 measurements or 12 measurement each hour.
If you are using the SAPCCM4X agent the number of measurements each hour will be at least 60. I know that this is still not the 240
measurements which we had before but at least it is much better then the 12 measurements.
Perhaps, in the further SAP can try to change something in the agent and collect the last 4 SAPOSCOL snapshots (if available) and in this way we also will get 240 measurements in the CCMS monitor segment each hour again.
-How to use SAP transaction ST06 for SAP performance analysis