Introduction
To help manage VeloCloud API rate limits—especially in environments with large data volumes, a new Use Optimized API Version (Recommended) option is available on the integration page.
When this option is enabled and a polling frequency is configured, the listed metrics are collected once at the integration level for all resources, based on the selected frequency. This occurs regardless of:
- Resource-level polling frequencies, and
- Whether templates containing these metrics are assigned to individual resources.
This optimization uses VeloCloud Enterprise-level APIs to retrieve data for all resources in a single request, dramatically reducing overall API usage and helping avoid 429 Rate Limit errors.
Alerting behavior remains unchanged and alerts continue to trigger according to the thresholds defined in the templates applied to each resource.
Metrics collected at the integration level:
vmware_sdwan_Edge_Statusvmware_sdwan_Edge_HA_Statusvmware_sdwan_Link_Statusvmware_sdwan_Link_VPN_Statevmware_sdwan_Link_Effective_Statevmware_sdwan_Link_Jittervmware_sdwan_Link_Latencyvmware_sdwan_Link_Bandwidthvmware_sdwan_Link_BandwidthPercentagevmware_sdwan_Link_Bytes_Sentvmware_sdwan_Link_Packet_Lossvmware_sdwan_Link_Packets_Sentvmware_sdwan_Link_Bytes_Receivedvmware_sdwan_Link_Packets_Receivedvmware_sdwan_Link_SignalStrengthvmware_sdwan_Link_Throughput