Multiple VROPS Instances to monitor different environments?

[mrstorey303]

I've heard from various sources that 'most' people deploy separate VROPs instances to manage their production infrastructure from their VDI infrastructure.

Our horizon stuff is deployed in a complete separate vsphere environment (different vcenters and SSO), and I did originally size the VROPs appliances to cater for both VDI and Production vSphere environments.

However now, after hearing what 'most' people do in what may be a possible best practice, I'm wondering whether I now need to deploy new appliances for non-VDI monitoring?

Anyone know why this is, or why I shouldn't just go ahead and use a single VROPs instance to monitor multiple environments?

The only limitation I can see is product dependancies - ie the latest Horizon mgmt pack doesn't yet support VROPS 6.7 - so maybe it's for reasons like this?

Any advice would be greatly appreciated - obviously the ideal would be to leverage the existing instance - saving on deploying and managing large appliances, so interested to hear what you all do, and / or why using a single instance could be a bad idea.

Thanks

[GayathriS]

Hi

About compatibility , yes you are rite Vrops for horizon is not supported with Vrops 6.7

The View adapter runs on a cluster node or remote collector node in vRealize Operations Manager. You can create a single View adapter instance to monitor multiple View pods. During broker agent configuration, you pair the broker agent with a View adapter instance. If you are monitoring multiple View pods, you can pair the broker agent installed in each pod with the same View adapter instance as long as the total number of desktops that the View adapter instance handles does not exceed 10,000. If you need to create multiple View adapter instances, you must create each adapter instance on a unique cluster node or remote collector.

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

regards

Gayathri

[mrstorey303]

I've noticed there's still many mgmt packs that don't support 6.7 yet - however the question was more around whether it's acceptable practice to use the same VROPs instance to manage both VDI and Production server infrastructure environments (separate vSphere environments).

[GayathriS]

Important  : Creating more than one Horizon adapter instance per cluster node or remote collector is not supported

https://docs.vmware.com/en/VMware-vRealize-Operations-for-Horizon/6.5/vrealize-horizon-64-installati...

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

regards

Gayathri

[RickVerstegen]

From my point of view you can go ahead monitoring with a single vROps instance. After the single vROps instance outgrows the existing size, you must expand the cluster to add nodes of the same size, so vROps is easy to scale up and to scale out as your environment grows. You need to keep an eye on the maximums, of course, which some are mentioned in the previous replies.

vROps has been developed to monitor multiple vCenter and horizon environments with a single instance, so keep it simple if you ask me. Why make it complex with multiple instances?

As you already mentioned, with this deployment model you can have product dependencies.

A reason why you maybe want multiple vROps instances / clusters if you want a development, test and production environment for vROps.

Hope this is helpful.

Rick

[mrstorey303]

Thanks - yep - that was my feeling too - I just can't see much benefit in splitting them out.

Presumably it's also possible to design a user's UI so they're not overwhelmed with the number of available dashboards, which may be a side effect of using a single instance to monitor multiple solutions / environments?

For example, if we had dedicated VDI Administrators, I could provide a filtered view so they only see the stuff that's relevant to them?

Thanks.

[RickVerstegen]

By using role based access you can define what users (for example VDI Administrators) can access and see within vROps UI.