In distributed vRealize Operations environments, remote collector nodes increase the inventory of objects that you can monitor without increasing the load on vRealize Operations in terms of data storage, processing, or analysis.
Prerequisites
- Create nodes by deploying the vRealize Operations vApp.
During vApp deployment, select a remote collector size option.
- Ensure any remote adapter instance is running on the correct remote collector. If you have only one adapter instance, select Default collector group.
- Create and configure the primary node.
- Note the fully qualified domain name (FQDN) or an IP address of the primary node.
- Verify that there is one remote collector already added before you add another remote collector.
Note: Remote collectors when added in parallel cause a cluster to crash.
Procedure
What to do next
After creating a remote collector node, you have the following options.
- New, unstarted clusters:
- Create and add data nodes.
- Create and add more remote collector nodes.
- Create a high availability primary replica node.
- Click Start vRealize Operations Manager to start the cluster, and log in to finish configuring the product.
The cluster might take from 10 to 30 minutes to start, depending on the size of your cluster and nodes. Do not make changes or perform any actions on cluster nodes while the cluster is starting.
- Established, running clusters:
- Create and add data nodes.
- Create and add more remote collector nodes.
- Create a high availability primary replica node, which requires a cluster restart.