X-ms-ratelimit-remaining-resource: Microsoft.Compute/HighCostGet30Min 0Ĭontent-Type: application/json charset=utf-8
X-ms-ratelimit-remaining-resource: Microsoft.Compute/HighCostGet3Min 46 A typical throttling error response from Compute Resource Provider will look like the example below (only relevant headers are shown): HTTP/1.1 429 Too Many Requests The 429 HTTP status is commonly used to reject a request because a call rate limit is reached. X-ms-ratelimit-remaining-resource: Microsoft.Compute/VmssQueuedVMOperations 4720 X-ms-ratelimit-remaining-resource: Microsoft.Compute/VMScaleSetBatchedVMRequests5Min 3704 X-ms-ratelimit-remaining-resource: Microsoft.Compute/DeleteVMScaleSet30Min 587 x-ms-ratelimit-remaining-resource: Microsoft.Compute/DeleteVMScaleSet3Min 107 Here is a sample response to delete virtual machine scale set request. There will be a separate x-ms-ratelimit-remaining-resource header for each policy. Note that an API request can be subjected to multiple throttling policies. Batch requests, such as for scaling a virtual machine scale set, can charge multiple counts. The number of call counts “charged” for this HTTP request toward the applicable policy’s limit. Remaining API call count for the throttling policy covering the resource bucket or operation group including the target of this request Call rate informational response headers Header Otherwise, the throttling is coming from the target resource provider (the one addressed by the /providers/ segment of the request URL). Activities by all subscription clients are counted together. If the remaining call count is approaching 0, the subscription’s general call limit defined by Azure Resource Manager has been reached. To understand if the request throttling is done by Azure Resource Manager or an underlying resource provider like CRP, inspect the x-ms-ratelimit-remaining-subscription-reads for GET requests and x-ms-ratelimit-remaining-subscription-writes response headers for non-GET requests. When an Azure API client gets a throttling error, the HTTP status is 429 Too Many Requests. Azure Resource Manager call rate limits and related diagnostic response HTTP headers are described here. Throttling by Azure Resource Manager vs Resource ProvidersĪs the front door to Azure, Azure Resource Manager does the authentication and first-order validation and throttling of all incoming API requests.
#AM I GETTING THROTTLED HOW TO#
This document describes API throttling, details on how to troubleshoot throttling issues, and best practices to avoid being throttled. We ensure all the calls to the Azure Compute Resource Provider (CRP), which manages resources under Microsoft.Compute namespace don't exceed the maximum allowed API request rate. Azure Compute requests may be throttled at a subscription and on a per-region basis to help with the overall performance of the service.
0 kommentar(er)
