vCenter database query - CPU ready

This came up when our team lead wanted a method for seeing global CPU ready values over a length of time to provide factual basis during performance audits.  The viclient performance tab only allows you to view one VM at a time, and compiling data from that manually is painful at best.

We thought about it a bit, then realized that all these historical statistics are stored in the vCenter database, so why not do a DB query to pull the relevant info?  I looked into it, and similar things have been done before.  With those as a basis for my query, I dug in to what was in the vCenter database and how to best present it.

What I ended up with is not as automated as I'd like, but good enough for being used once or twice a year for audits.  This one was a lot of fun!

Full article on the wiki:


Popular posts from this blog

Fixing duplicate SPNs (service principal name)

DFSR - eventid 4312 - replication just won't work

Logstash to Nagios - alerting based on Windows Event ID