The Monitoring Load step shows:
|•||Monitoring Group(s). In this configuration, there is only one monitoring group, named Default Monitoring Group (this group may be renamed in the Veeam UI).|
|•||New Jobs and Existing Jobs in each group. In this situation, there are no existing jobs, as this is the first vCenter Server to be added.|
|•||Monitoring Jobs. By default, each vSphere cluster equals one job. There will also be a job for all datastores in this vCenter Server, and a placeholder for future jobs (to show where new clusters added to this vCenter Server will be placed, as and when discovered). In this example, there are 2 existing clusters in this vCenter Server.|
|•||Monitoring load. The load is calculated according to the total number of objects (hosts, VMs, datastores and so on) in the target vCenter Server. The total monitoring load for the whole monitoring group (existing jobs plus new jobs) is also shown.|
|•||Recommended Collectors. Based on the monitoring load, the number of recommended Veeam Collector servers will be displayed. |
|•||License status: expiry date, and required and available sockets.|
In the requirements for this example, monitoring load is well within limits for the one available Collector. Both clusters are required to be monitored. All targets added in future should also be monitored automatically, and all jobs should be placed in the same (default) monitoring group.
No further configuration is required. Click Finish to add this vCenter Server target for monitoring by the Veeam Virtualization Extensions.