javascript:void(0)

Wednesday, August 3, 2011

Hidden vCenter Debugging Performance Metrics



While extracting the new performance metrics in vSphere 5 for a blog post, I came across a metric type that I had never noticed before, vcDebugInfo. These performance metrics seems to deal with some of the internal performance/counters in vCenter such as lock statistics, MoRef (Managed Object Reference) counts, etc. Majority of these metrics are available in either collection level 1 or 4 which is the highest level containing all statistics. VMware's best practice is to only enable collection level 1 or 2, 3 and 4 should only be enabled under VMware supervision for debugging purposes which is most likely when some of these stats may come in handy. So be warn, these are probably not supported by VMware

I found it interesting that these metrics are hidden from the vSphere Client UI, but they can easily be extracted when going through the vSphere API. It is just amazing on all the goodies you can find when going through the APIs :)

MetricStat LevelDescription
vcDebugInfo
maximum.millisecond.activationlatencystats4The latency of an activation operation in vCenter
minimum.millisecond.activationlatencystats4The latency of an activation operation in vCenter
summation.millisecond.activationlatencystats1The latency of an activation operation in vCenter
maximum.number.activationstats4Activation operations in vCenter
minimum.number.activationstats4Activation operations in vCenter
summation.number.activationstats1Activation operations in vCenter
maximum.millisecond.hostsynclatencystats4The latency of a host sync operation in vCenter
minimum.millisecond.hostsynclatencystats4The latency of a host sync operation in vCenter
summation.millisecond.hostsynclatencystats1The latency of a host sync operation in vCenter
maximum.number.hostsyncstats4The number of host sync operations in vCenter
minimum.number.hostsyncstats4The number of host sync operations in vCenter
summation.number.hostsyncstats1The number of host sync operations in vCenter
maximum.number.inventorystats4vCenter inventory statistics
minimum.number.inventorystats4vCenter inventory statistics
summation.number.inventorystats1vCenter inventory statistics
maximum.number.lockstats4vCenter locking statistics
minimum.number.lockstats4vCenter locking statistics
summation.number.lockstats1vCenter locking statistics
maximum.number.lrostats4vCenter LRO statistics
minimum.number.lrostats4vCenter LRO statistics
summation.number.lrostats1vCenter LRO statistics
maximum.number.miscstats4Miscellaneous statistics
minimum.number.miscstats4Miscellaneous statistics
summation.number.miscstats1Miscellaneous statistics
maximum.number.morefregstats4Managed object reference counts in vCenter
minimum.number.morefregstats4Managed object reference counts in vCenter
summation.number.morefregstats1Managed object reference counts in vCenter
maximum.number.scoreboard4Object counts in vCenter
minimum.number.scoreboard4Object counts in vCenter
summation.number.scoreboard3Object counts in vCenter
maximum.number.sessionstats4The statistics of client sessions connected to vCenter
minimum.number.sessionstats4The statistics of client sessions connected to vCenter
summation.number.sessionstats1The statistics of client sessions connected to vCenter
maximum.number.systemstats4The statistics of vCenter as a running system such as thread statistics and heap statistics
minimum.number.systemstats4The statistics of vCenter as a running system such as thread statistics and heap statistics
summation.number.systemstats1The statistics of vCenter as a running system such as thread statistics and heap statistics
maximum.number.vcservicestats4vCenter service statistics such as events, alarms, and tasks
minimum.number.vcservicestats4vCenter service statistics such as events, alarms, and tasks
summation.number.vcservicestats1vCenter service statistics such as events, alarms, and tasks

0 comments:

Post a Comment

 
/*http://blog.cartercole.com/2009/10/awesome-syntax-highlighting-made-easy.html*/