In our test environment, we do have this ClusterComputeResourcePerf source from vc4.1 and vc5.1.
1 » 2/22/13
2:15:00.000 AM
2013-02-21 18:15:00 UTC, fa=bt,vc=vc4, vmoid=domain-c1284,meid="vc-4521FD10-9C19-45E4-BA15-F7AFF71A92FF:domain-c1284", moname=Test, perftype=mem, AvgVmctl_KB=0.00, AvgConsum_KB=0.00, AvgOvrhd_KB=0.00, AvgUsg_pct=0.00, perftype=mem
host=vc4pw Options| sourcetype=vmware:perf Options| source=ClusterComputeResourcePerf Options
2 » 2/22/13
1:20:00.000 AM
2013-02-21 17:20:00 UTC, fa=bt,vc=vc5, vmoid=domain-c72,meid="vc-16C04DD2-4B51-4721-9FE3-338F5F443E9E:domain-c72", moname=cl5pw, perftype=mem, AvgVmctl_KB=0.00, AvgConsum_KB=97987861.00, AvgCap.Entitle_KB=94567705.00, AvgTot_mb=180456.00, AvgCap.Usg_KB=24005321.00, AvgOvrhd_KB=1350884.00, AvgUsg_pct=49.35, perftype=mem
host=vc5pw Options| sourcetype=vmware:perf Options| source=ClusterComputeResourcePerf Options
So, can you please check if you can see those counters from vCenter?
For the issue you mentioned above "ReadSubKeys($discovery, "->Status->Conn->vim_service->vim_soap->user_agent->cookie_jar->COOKIES->${host}->/->vmware_soap_session");", the reason is the ${host} is "vc-server". But, the HTTP::Cookie::add_cookie_header does:
$domain = "$domain.local" unless $domain =~ /./;
So, the correct path to get soap_session for short name server is,
"my $soap_session = ReadSubKeys($discovery, "->Status->Conn->vim_service->vim_soap->user_agent->cookie_jar->COOKIES->${host}.local->/->vmware_soap_session");"
This is a known issue in 1.0.1 release note, and it is fixed in later version. Thanks.
... View more