A remote collector node is an additional cluster node that allows vRealize Operations to gather more objects into its inventory for monitoring purposes. Unlike the data nodes, the remote collector nodes only perform the collector role of vRealize Operations. These remote collectors do not store data or process any analytics functions. Remote collectors collect data from integrated objects and then forward the data back to the primary node. The primary node then processes the data which you then view as reports and analytics.

Remote collectors are very useful when you have multiple locations. You can deploy remote collectors on remote location sites and only deploy the primary node at the primary location.

You must have at least one primary node before adding remote collector nodes.

A remote collector node is usually deployed to navigate firewalls, reduce bandwidth across data centers, connect to remote data sources, or reduce the load on the vRealize Operations analytics cluster. To deploy a remote collector node, see Run the Setup Wizard to Create a Remote Collector Node.

Remote collectors do not buffer data while the network is experiencing a problem. If the connection between the remote collector and the analytics cluster is lost, the remote collector does not store data points that occur during that time. In turn, and after the connection is restored, vRealize Operations does not retroactively incorporate associated events from that time into any monitoring or analysis.

Ports information for vRealize Operations is available on Ports and Protocol.