Network Management

Viptela API polling limit was exceeded

By default, SolarWinds Hybrid Cloud Observability limits API requests for Viptela orchestrators to 50 requests per second. If the limit is exceeded, configure further limitations for Viptela polling.

First published date

7/25/2023 8:27 AM

Last published date

7/25/2023 8:27 AM

Overview

A Viptela Orchestrator is limited to 100 requests per second. By default, SolarWinds Hybrid Cloud Observability limits the requests to 50 per second. If the limit is exceeded, you will receive an Event and the Details widget on the Orchestrator Node Details page will also inform you that the Viptela API polling limit was exceeded. See Resolution for tips on how to limit SolarWinds requests.

Product section

Network Performance Monitor

Cause


The maximum number of allowed Viptela 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 Hybrid Cloud Observability.

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.Viptela.
  4. Adjust the responses caching to share responses to similar requests between polling jobs on your polling engine. Increase values for the following settings to reduce the number of requests sent to the API.
    • 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.
    • 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.
    • RequestsLimit: Limits the number of requests to Viptela API per limitation period. By default, this is set to 50. The default value is half of the general Viptela Orchestrator requests limit to prevent possible overloading of the Viptela Orchestrator API. Reduce this setting to reduce the number of API requests.
    • RequestsLimitationPeriod: The limitation period. By default, this is set to 00:00:01 (one second). Make the limitation period longer to reduce the number of API requests.
  6. Click Save to apply your changes.