VMware Cloud Community
mrstorey303
Enthusiast
Enthusiast

Monitor Subset of vSphere Objects - Best Practices?

What is the correct or best practice method for limiting which objects are monitored with vROPS due to licensing?  Is it really as simple as putting 'no access' permissions on the datacenter and host objects you don’t want vROPS to monitor?

For example - we have a decent sized vSphere environment - 3 vcenters in linked mode, 30+ sites, several hundred hosts.  But, only a subset of these hosts have vROPS licensing.  What is the best approach for configuring vROPs so you’re compliant, and don’t receive noise from sites and hosts you don’t want to monitor with vROPS?

Are you really supposed to limit the permissions given to the collector account?  Or is there a better way with custom groups etc?  Maybe something else?

I’m probably missing something, but I don’t really understand why VROPs doesn’t automatically ignore any host which isn't licensed with a vROPS key?

Reply
0 Kudos
2 Replies
filosmith
Enthusiast
Enthusiast

We have a similar licensing setup. Our sales engineer told us to simply deny access to the unlicensed hosts for the service account that vROPS uses.

MeImNot76
Enthusiast
Enthusiast

I was nearly in your same situation where I wanted to monitor the entire vCenter infrastructure but not some of the VMs (customer VMs). I tried the permissions route but I felt like it was getting too messy, I ended up solving it this way:

Created custom group 'Customer VMs' with criteria to capture only our customer VMs

Edit License Group, in the Virtual Machine part of the membership criteria I added this criteria: Relationship Descendant of is not 'Customer VMs', which basically won't allow VMs that form part of the 'Customer VMs' custom group to get a license. As soon as you refresh the Licensing (from the License Keys tab), you will see the Unlicensed group getting populated.

It has been working well and in a dynamic way for over two months now.