The vRealize Operations Management Pack for NSX Advanced Load Balancer collects metrics and properties for several object types.
|Controllers||Single point of management and control that serves as the brain of the entire system. For high availability, the controller is typically deployed as a three-node cluster. The controller implements the control plane.|
|Tenants||Isolated instances of the NSX Advanced Load Balancer that are associated with a user account that defines the resources that a user has access to.|
|Clouds||Containers for the environment that the NSX Advanced Load Balancer is installed in or operating within.|
|Virtual Services||Objects that advertise an IP address and ports to the external world and listen for client traffic. When the virtual service receives traffic, it can be configured for different reasons.|
|Pools||Objects that maintain the list of servers assigned to them and performs health monitoring, load balancing, persistence, and functions that involve NSX Advanced Load Balancer-to-server interaction.|
|Servers||The service engine machine. This can either be an EC2 instance/Azure Virtual Machine/Compute Instance/vCenter Virtual Machine.
Note: A prerequisite to view this object type is to add the cloud account, which is, vCenter/AWS/Azure/GCP, in vRealize Operations where the service engine is deployed. This helps to monitor the actual service engine machine.
|Service Engines||Machines that host the virtual services and require either direct or routable access to the client and server network.|
|Service Engine Groups||Objects that contain the definition of how the service engines should be sized, placed, and made highly available.|
|Network||Network resources used by service engines to communicate with the controller. This may be the same network as one of the data networks used for load balancing.|
For more details about object types, see the Avi Documentation.
The flow chart depicts the hierarchy of the supported objects types.