Network Management

VeloCloud API polling limit was exceeded

A VeloCloud Orchestrator is limited to 500 requests every five seconds per each type of user (Operator, Partner, and Customer). SolarWinds Hybrid Cloud Observability does not send more requests than this limit. However, when other requests to Dashboard API are sent for the same organization, the limit can be reached. You will receive an Event and the Details widget on the Orchestrator Node Details page will also inform you that the VeloCloud API polling limit was exceeded. See Resolution for tips on how to limit SolarWinds Observability requests.

First published date

11/22/2022 7:43 AM

Last published date

2/15/2023 10:35 AM

Overview

A VeloCloud Orchestrator is limited to 500 requests every five seconds per each type of user (Operator, Partner, and Customer). 
SolarWinds Hybrid Cloud Observability does not send more requests than this limit. However, when other requests to the Orchestrator API are sent for the same organization, the limit can be reached. See Rate Liming APIs in VMware documentation (© 2022 VMware, Inc., available at https://docs.vmware.com, obtained on September 12, 2022).

If the limit is exceeded and retrying the request doesn't help, you will see a warning box in the Details widget on the Orchestrator's Node Details page and an "Orchestrator API polling limit was exceeded" event.

See Resolution for a workaround.

Product section

Orion Platform

Cause

The maximum number of allowed VeloCloud API requests was exceeded.

Resolution

If you cannot turn off the additional sources of API requests, consider configuring additional limits to be enforced in SolarWinds Observability or disabling polling VPN tunnels.

Configure additional limits

  1. Log in to the SolarWinds Platform Web Console using an account with administrative privileges.
  2. Copy /Admin/AdvancedConfiguration/Global.aspx and paste it into your browser address bar, after /Orion. See Access the Advanced Configuration settings in the Orion Web Console.
  3. Now in Advanced Configuration Settings, search for Orchestrators.VeloCloud.
  4. Adjust the responses caching to allow sharing responses of similar requests between polling jobs within the appropriate polling engine.
    • RequestMaxWait: Specifies the time the rate limiter waits for a free execution slot before the request fails. The default value is 1 minute, formatted as 00:01:00. If appropriate, decrease the wait time. To configure requests to fail when there is no free execution slot, enter 00:00:00.
    • RequestRetries: Specifies how many times a request is resent if it fails. The default value is 2.
    • InventoryRequestsCacheTimeToLive: Time to live for inventory requests cache item. The default value is 5 minutes.
    • PollingRequestsCacheTimeToLive: Time to live for the polling requests cache item. The default value is -1 minute, which means that TimeToLive is equal to the polling interval of a poller that makes the request.
  5. Adjust the rate limits on the SolarWinds Platform side to control how many API calls the platform performs within a specific time period. If appropriate, change the number of requests per second to a smaller number.
    • RequestsLimit: Limits the number of requests to VeloCloud API per limitation period. By default, this is set to 250. The default value is half of the general VeloCloud Orchestrator requests limit to prevent possible overloading of the VeloCloud Orchestrator API.
    • RequestsLimitationPeriod: The limitation period. By default, this is set to 00:00:05 (five seconds).
  6. Click Save to apply your changes.

Disable polling VPN tunnels (2023.1 and later)

  1. Log in to the SolarWinds Platform Web Console using an account with administrative privileges.
  2. Click Settings > All Settings, and then click Polling Settings.
  3. Scroll down to VeloCloud settings, clear the Poll VPN Tunnels box, and submit the changes.
VPN tunnel data will no longer be polled from VeloCloud devices. After the polling is disabled, historical data will stay in the database.