Skip to content

Commit 5ab28e6

Browse files
Merge pull request #303738 from dlepow/patch-788246
[APIM] Update backends.md - Circuit breaker for AOAI backend
2 parents 06fcf21 + 9d1918a commit 5ab28e6

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/api-management/backends.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,9 @@ The backend circuit breaker is an implementation of the [circuit breaker pattern
128128
> * Because of the distributed nature of the API Management architecture, circuit breaker tripping rules are approximate. Different instances of the gateway do not synchronize and will apply circuit breaker rules based on the information on the same instance.
129129
> * Currently, only one rule can be configured for a backend circuit breaker.
130130
131+
> [!CAUTION]
132+
> If you configure an Azure OpenAI service as a backend and the service receives too many requests, it returns a `429 Too Many Requests` response status code and a `Retry-After` header with a value that can be large (for example, 1 day). With Azure OpenAI backends we recommend implementing circuit breaker rules to handle the `429` responses and accept the `Retry-After` duration.
133+
131134
### Example
132135

133136
Use the Azure portal, API Management [REST API](/rest/api/apimanagement/backend), or a Bicep or ARM template to configure a circuit breaker in a backend. In the following example, the circuit breaker in *myBackend* in the API Management instance *myAPIM* trips when there are three or more `5xx` status codes indicating server errors in 1 hour.

0 commit comments

Comments
 (0)