Metrics are missing for NSX Transport Nodes

Products

• VMware Aria Operations 8.x

Issue/Introduction

These symptoms can be seen:

• Some metrics are not showing in the metrics list.
  
  
• Collection points are missing or not showing at regular intervals. 

 

In the NSX adapter logs located in /storage/log/vcops/log/adapters/NSXTAdapter/NSXTAdapter_######.log, this kind of errors shows:

2025-03-30T08:58:14,781+0000 ERROR [NSX-T Metric Collector thread 11, time: Sun Mar 30 08:58:13 GMT 2025] (189280) com.vmware.adapter3.nsxt.util.NsxtApiUtil.getTransportNodeInterfaceStatistics - Node Interface Statistics properties not retrieved due to 429 error, retrying the API. The exception caused is com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
    messages = [],
    data = struct => {error_message=Client '[email protected]' exceeded request rate of 100 per second, error_code=102, module_name=common-services},
    errorType = SERVICE_UNAVAILABLE
}
2025-03-30T08:58:14,793+0000 ERROR [NSX-T Resource Collector thread 5, time: Sun Mar 30 08:58:13 GMT 2025] (189280) com.vmware.adapter3.nsxt.util.NsxtApiUtil.getSearchResults - Search Response not retrieved due to 429 error, retrying the API for query : resource_type:VirtualNetworkInterface
2025-03-30T08:58:14,933+0000 ERROR [NSX-T Resource Collector thread 16, time: Sun Mar 30 08:58:13 GMT 2025] (189280) com.vmware.adapter3.nsxt.util.NsxtApiUtil.getManagementNodeInterfacePropertiesListResult - Node interface properties not retrieved due to 429 error, retrying the API
2025-03-30T08:58:14,934+0000 ERROR [NSX-T Resource Collector thread 16, time: Sun Mar 30 08:58:13 GMT 2025] (189280) com.vmware.adapter3.nsxt.util.NsxtApiUtil.getManagementNodeInterfacePropertiesListResult - Exception caused is:
com.vmware.vapi.std.errors.ServiceUnavailable: ServiceUnavailable (com.vmware.vapi.std.errors.service_unavailable) => {
    messages = [],
    data = struct => {error_message=Client '[email protected]' exceeded request rate of 100 per second, error_code=102, module_name=common-services},
    errorType = SERVICE_UNAVAILABLE
}

Environment

Aria Operations 8.x

Cause

An HTTP 429 error indicates that the user has sent too many requests in a given amount of time. This is often referred to as a "rate limit" error.
The Management Pack pulls properties and metrics from the NSX server, if there is no data from NSX side in a cycle, some metrics or properties will not be recorded for that collection cycle.

Resolution

To avoid this issue, increase the rate limit on the NSX server side.
Refer to NSX-T API configuration for HTTP on NSX-T Manager.

Note: Increasing the default rate limit may impact the performance on the NSX side. The user needs to evaluate the need and trade-off. The value needs to be reverted to default if any issue.