Often times what you get out of the box isn’t exactly what you need. The great thing about vRealize Operations is that it is quite customizable – from its great dashboarding capabilities, reporting, capacity planning, to policies, which allow for customizing how vRealize Operations treats different groups of resources. In this blog, we’ll explore how relationships can manually be created between resources – which helps admins understand how performance and availability of a resource is related to the performance and availability of it’s dependent resources. Additionally, we’ll take a look at collection intervals and how they can be customized to accommodate business requirements.
Most quality third-party management packs for vRealize Operations Manager (vROps) will create relationships to other resources where it makes sense. Sometimes additional relationships would be helpful to understand the impact between various dependent resources. In this example, we’ll create a relationship between a vCenter server and the PostgreSQL database sitting on it. The vCenter server resources are brought in via the vSphere adapter and PostgreSQL resources via the Blue Medora Management Pack for PostgreSQL.
Figure 1 – Manually Creating Relationships in vRealize Operations
By default, most management packs will have a collection interval of five minutes. This is typically sufficient to capture operational data in order to determine general trends. There is a significant load on vRealize Operations if you reduce this collection interval, as it has to store the data in memory, perform analytics against the data, etc. Sometimes though, it can be necessary to monitor at a more granular level.
Figure 2 – Changing Collection Interval
Figure 3 – Changing the collection interval
Now that you have an understanding of how to manually create relationships between objects and set custom collection intervals, you’re on your way to having an even more successful vRealize Operations Manager implementation. Keep you eye out for my next blog on using maintenance to suppress analytics and alerting for resources.
This blog post first appeared on VMware Cloud Management Blog. To read the full article, click here.