Hi
I'm sorry if this was already discusses and I missed it.
There is a difference between VI API 2.5 and 4.0 cluster performance data and I was wondering if this is expected.
In short, the PerfCounterInfo array returned by QueryPerfCounter In API 2.5 is always larger than corresponding PerfEntityMetric array returned by QueryPerf, but in 4.0 it's the opposite.
Precisely, in 4.0 I run into situation when I receive values with keys that are NOT available for a particular managed object.
This happens because QueryAvailablePerfMetric, which I call without the interval id assigned, in 2.5 returned more number of metric ids than I'd later receive values, but in 4.0 it returns less.
As I said, it happens only with clusters.
Any comment, please?
Thanks a lot in advance.
I'm sorry if this was already discusses and I missed it.
There is a difference between VI API 2.5 and 4.0 cluster performance data and I was wondering if this is expected.
In short, the PerfCounterInfo array returned by QueryPerfCounter In API 2.5 is always larger than corresponding PerfEntityMetric array returned by QueryPerf, but in 4.0 it's the opposite.
Precisely, in 4.0 I run into situation when I receive values with keys that are NOT available for a particular managed object.
This happens because QueryAvailablePerfMetric, which I call without the interval id assigned, in 2.5 returned more number of metric ids than I'd later receive values, but in 4.0 it returns less.
As I said, it happens only with clusters.
Any comment, please?
Thanks a lot in advance.