You can add, edit, or remove collector groups in vRealize Operations, and rebalance your adapter instances.
Rebalancing an Adapter Instance
Rebalancing of your adapter instances is not intended to provide equally distributed adapter instances across each collector in the collector group. The rebalancing action considers the number of resources that each adapter instance collects to determine the rebalancing placement. The rebalancing happens at the adapter instance, which can result in several small adapter instances on a single collector, and a single huge adapter instance on another collector, in your vRealize Operations instance.
Rebalancing your collector groups can add a significant load on the entire cluster. Moving adapter instances from one collector to another collector requires that vRealize Operations stops the adapter instance and all its resources on the source collector, then starts them on the target collector.
If a collector fails to respond or loses connectivity to the cluster, vRealize Operations starts automated rebalancing in the collector group. All other user-initiated manual operations on the collector, such as stopping or restarting the collector manually, do not result in automated rebalancing.
If one of the collectors fails to respond, or if it loses network connectivity, vRealize Operations performs automated rebalancing. In cases of automated rebalancing, to properly rebalance the collector group, you must have spare capacity on the collectors in the collector group.
Where You Manage Collector Groups
From the left menu, click Administration, and then click the Collector Groups tile.
Options | Description |
---|---|
Collector Group toolbar | To manage collector groups, use the toolbar icons.
|
Collector Group Name | The name given to the collector group when the collector group is created. |
Description | Description given to the collector group when the collector group is created. |
Application Monitoring High Availability Status | Displays the application monitoring high availability status of the collector group.
Note: For default collector groups, high availability for application monitoring is deactivated by default.
|
Virtual IP | Virtual IP address of the collector group.
Note: Pick the Virtual IP address that any of the cloud proxies in a collector group can own and receive traffic from. The Virtual IP address must be in the same subnet as the physical address of the cloud proxies. After you configure the Virtual IP address, ping it from a different network to ensure that it is routable.
|
Filters | Search the list of collector groups according to the following criteria:
|
Quick Filter Name | Filters the list of collector groups according to the name of the collector group entered. |
Click a collector group to view the collector group details.
Detail Grid Options | Description |
---|---|
Collector Group Name | Displays the name of the collector group. Click Edit to modify the collector group details. Click View Description to view the collector group description. |
Application Monitoring High Availability Status | Displays the status of the application monitoring high availability. |
Virtual IP | Displays the virtual IP added during the collector group creation. |
Name | Name given to the cloud proxy when the collector was created |
IP Address | IP address of the cloud proxy |
Status | Status of the cloud proxy: online or offline. |
Number of Objects | Displays the number of objects collected by the cloud proxy. |
Number of Adapter Instances | Displays the number of adapters using the cloud proxy. |