You can export network latency statistics to external collectors and run analytics on the data. The netopa agent that is running in the ESXi hosts can export the network latency statistics only to Aria Operations for Networks. Other collector tools are not supported currently.
You can collect network latency statistics from only vCenter-managed ESXi hosts. Collecting latency statistics from standalone ESXi hosts is not supported.
- Method 1: Use the management plane APIs in NSX.
- Method 2: Enable an optional setting in the Aria Operations for Networks UI to collect latency statistics.
Prerequisites
- In the Aria Operations for Networks UI, complete the following tasks in the given order:
- Add VMware vCenter as the data source. If you have multiple vCenter Servers added as Compute Managers in your NSX environment, you can add all vCenter Servers as the data source.
- Add NSX Manager as the data source.
For detailed information about adding data sources in Aria Operations for Networks, see the Aria Operations for Networks documentation.
- Ensure that port 1991 is open on the collector to receive network latency data from the ESXi hosts.
Procedure
Results
vNIC-to-vNIC latency statistics are exported to the external collector in the following format:
VIF1, VIF2, Max, Min, Avg- VIF1, VIF2 represent the virtual interfaces or the vNICs.
- Max, Min, and Avg represent the maximum, minimum, and average time between the two vNICs in microseconds.
pNIC-to-vNIC and vNIC-to-pNIC latency statistics are exported to the external collector in the following format:
Endpoint1, Endpoint2, Max, Min, Avg- Endpoint1, Endpoint2 can either be the virtual interface ID (VIF ID) or the name of the physical adapter on an ESXi host (vmnic).
- Max, Min, and Avg represent the maximum, minimum, and average time between the two endpoints in microseconds.