Monitoring VMware vCenter Health Remotely with vRealize Operations – Part 3
In Part 1 and Part 2 of this blog, I discussed how you can monitor vCenter’s databases remotely using Blue Medora’s Management Pack for PostgreSQL and Microsoft SQL. Monitoring database performance is important to understanding the performance and health of your vCenter server, but it is just as import to understand the performance and health of the vCenter server itself. In this blog, we’ll take a look at vCenter specific metrics, best practices, and how you can monitor these with vRealize Operations Manager.
First, it is important to understand the best practices and to identify which performance metrics really matter when monitoring vCenter. For this, we will take a look at VMware’s Technical White Paper “VMware vCenter Server Performance and Best Practices.” This white paper addresses key performance indicators for vCenter health and performance, as well as capacity metrics to watch. We see that CPU, Memory, Disk I/O, Network Throughput, Network I/O, and Concurrency (number of vCenter operations run currently) are the key indicators for performance and capacity.
Luckily, vRealize Operations provides most of the key metrics we need to monitor. Additionally, we can leverage vRealize Operations’ analytics to understand both the capacity and stress of our vCenter server. After selecting your vCenter server on this custom dashboard, a number of key widgets will give you insights into your vCenter server performance and capacity.
Down the left-hand column we have three indicators:
Read the entire article here, Monitoring vCenter Health Remotely with vRealize Operations – Part 3
via the fine folks at VMware!