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.

Below metrics are collected by default when this option is enabled:

  • vmware_sdwan_Edge_Status
  • vmware_sdwan_Edge_HA_Status
  • vmware_sdwan_Link_Status
  • vmware_sdwan_Link_VPN_State
  • vmware_sdwan_Link_Effective_State
  • vmware_sdwan_Link_Jitter
  • vmware_sdwan_Link_Latency
  • vmware_sdwan_Link_Bandwidth
  • vmware_sdwan_Link_BandwidthPercentage
  • vmware_sdwan_Link_Bytes_Sent
  • vmware_sdwan_Link_Packet_Loss
  • vmware_sdwan_Link_Packets_Sent
  • vmware_sdwan_Link_Bytes_Received
  • vmware_sdwan_Link_Packets_Received
  • vmware_sdwan_Link_SignalStrength
  • vmware_sdwan_Link_Throughput

For alerting to work on this metrics, template should be applied for the particular resource and alert thresolds should be configured.