QueryPerf against ESX 3.5 host connected via a vCenter 4.0 works fine - but not against an ESXi 4.0 host

[Athadu]

Hi,

We are using the VI SDK 2.5 from Windows XP SP3. Also, tried with the latest vi-sdk-4.0.0-161137 SDK - with same results.

We are using QueryAvailablePerfMetric call to get the metric ids and using them in a subsequent call to QueryPerf to get the perf data.

a. Connection via vCenter 4.0 to ESXi 3.5 - returning back the perf data for host and VMs fine.

b. Connection via vCenter 4.0 to ESXi 4.0 - returning back the perf data for the VMs on the ESXi 4.0 host fine - but not the perf data for the host itself. QueryPerf returns back with an empty array for the call to query the host perf data.

c. Connection directly to the ESXi 4.0 host - QueryPerf returns back data for host and VMs fine.

I verified that the times on my client machine, vcenter server and the ESX hosts are in sync and with no time diff.

I appreciate any insight into why QueryPerf is not returning back the data in case-b above.

I am attaching a sample VS2005 solution where I am able to reproduce it consistently in our environment.

BTW, I checked the following thread - they seem to be discussing the same topic - but none of them seem to conclude a real solution.

http://communities.vmware.com/message/1269593#1269593

http://communities.vmware.com/message/1492776#1492776

Regards

-Athadu

[Athadu]

Hi

After further research - found this from the VMware knowledge base at

-

---

"Values for metric counters are integers. This issue occurs if a metric counter has a value that exceeds the integer limit. A single problematic counter can cause the whole query to return an empty result."

To workaround this issue, perform one of these options:

• Query the vCenter Server for the remaining metrics, one at a time. This allows you to retrieve values for metrics that do not exceed the integer limit.
  
  Note: This option is slow and puts an extra load on the vCenter Server.

• Query the information directly from the ESX host.

-

---

Now my question is - when/if VMware will have a fix for this - some kind of a estimated date; Querying for each metric one at a time is not a good option in our case; neither going directly to the ESX Host.

I would greatly appreciate any input from a VMWare support pro in this regard.

Regards

[admin]

Hi,

This is a known issue. The fix for the same is expected to be available in upcoming VC update releases.

Thanks,

Angela

[Athadu]

Thank you Angela for the reply.

Is there a planned date, or an approximate timeframe, for the VC update release that will have a fix for this issue? This is turning out to be a show stopper for our customers and we want to set some expectations about the fix for them.

Again, thank you for your greatly appreciated efforts in answering the questions on the forum.

Regards

[cruiser_csuf]

So how do you query directly against the ESX host? Do you use the same webservice? Or is there away to get it routed to the ESX server?