The Monitoring Load step shows:
|•||Monitoring Group(s). All new jobs have been initially placed in the Production monitoring group, because this was originally the Default Monitoring Group. Even after renaming, this group is still internally marked as the default group for new jobs and new Collectors. |
|•||New Jobs and Existing Jobs in each group. In this situation there are no existing jobs, as this is the first vCenter Server target 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, when discovered). In this example, there are two 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 two available Collectors. Both clusters are checked and will be monitored. All tagets added in future will be monitored automatically, and all new jobs for this vCenter Server will be placed in the same Production monitoring group.
No further configuration is required. Click Finish to add this vCenter Server target for monitoring by the Veeam Virtualization Extensions.