Hi there,
i'am also playing around with Performance Querys.
primary for all the "Summation" counters i have a Problem.
For example Vmware advice that "CPU Ready" should not be higher then 5%. so 5%=1000ms.
in this Case i'am not quiet sure, but i think theire where some changes around Esx 3.5 U1. i don't remember but since an special Version the -IntervalSecs 20 was not working anymore correct. and the Code was not changed for Vsphere as a VM Technical Support told me.
i opend several Cases because of following Problem:
for example:
A costumer told me that he has some Problems with his VM. He ments Performance Problem, but could't not exactly clarify which counter exactly.
so in this Case it was also interesting to check "CPU Ready" how long the CPU was waiting for his CPU Ressources
But it seems to be that their are some Problems, because it's not possible to query an ~usable Value for a specified time (last day, week, month, costum).
the strange thing is, i will not get the correct Value for (summation counters) which the VM had at the Problem time. also little problem with other Rollup Stat "average" counters
i attach some pictures.
i had theire 2 Problems:
1: ver high cpu load in ~ 5 min Steps (>90% cpu load)i marked a time (07:10:40) Live-Time1.jpg
i made an costum Chart to have a backward sight:2 hours back. so i marked nearly the same time (07:10:00) Cotum1.jpg
So at this time the CPU Load was at about >26%. and no grave changes. so these are very high differences.
so these seems to be that they are not working anymore with 20sec interval
2: Query for CPU-Ready
real-time.jpg
lastday.jpg
costum-chart.jpg
so as more, longer i queryied Backward as higher was the output value.
so in this case it's nearly not possible that a VM had 31431 ms Ready value. this would be 155% ready value.
They checked nearly everything, and told me that this is marked official as a "Bug" and was forwarded to the Developers.
So until now with Vsphere U1, Problem still exists and i couldn't tell my costumer how high was the value in a specified time.
we had to avoiding this right now with "Nworks" Monitoring to have an external Database. we also trying to use the new Alert-triggers für a special Condition Time of CPU-Ready.
Best Regards
Max