VMware vCenter Extractor Service
You can use the VMware vCenter Extractor Service ETL to continuously collect the configuration and performance metrics of vCenter servers from your VMware environment.
When your VMware environment is large, you can configure multiple ETLs and use the import filter option in the Advanced configuration to split the vCenter entities between them. To determine the number of ETLs that are required to collect data from your VMware environment, see the following sizing guideline:
With BMC Helix Capacity Optimization, you can manage very large vSphere environments containing multiple vCenters.
The vCenter Extractor Service is a "service connector". When sizing the ETL Engines, follow the guidelines for service connectors. If you have a very large vCenter, you may have to deploy multiple extractors against it.
Specifically for the vCenter Extractor Service, the main drivers for sizing are:
- Number of VMs
- Number of managed clusters
Use the following rules:
- No more than 2,000 VMs per ETL
- Scheduler heap: 2 GB for the first 2,000 VMs, and 1 GB for 2000 VMs thereafter
- Data storage on the ETL Engine machine: 10 GB per 2,000 VMs
For heavily populated clusters, the 2,000 VMs in the above rules can be equated to a single cluster. If you have many small clusters, consider that the number of clusters affects the number of threads used by the vCenter Extractor Service; allow enough CPU resources to ensure timely polling of data by limiting the number of clusters for each vCenter extractor.
The following video (2:35) illustrates the process of setting up a VMware - vCenter Extractor Service ETL.
Collecting data by using the VMware vCenter Extractor Service ETL
To collect data by using the VMware vCenter Extractor Service ETL, do the following tasks:
II. Configure the ETL.