Standard service bus Throttled Requests metric

Question

Standard service bus Throttled Requests metric

Wang Meihua 175

In "Throttling in premium tier" section, https://docs.azure.cn/en-us/service-bus-messaging/service-bus-throttling#throttling-in-premium-tier, it states "Throttled Requests show up on the Azure Monitor Request metrics to identify how many requests were throttled.", we are using Standard tier, wanted to confirm if Throttled Requests metric is also available in Standard tier? if so, in what scenarios Throttled Requests will be recorded in service bus Standard? thank you very much. User's image

0 comments

Answer accepted by question author

Pravallika KV 18,850 Microsoft External Staff Moderator

Hi @Wang Meihua ,

Yes, the “Throttled Requests” metric isn’t exclusive to Premium – it also shows up for Standard namespaces in Azure Monitor under the Service Bus Request metrics. In Standard you have credit-based throttling, so whenever you exhaust your per-second credits, any further calls get throttled and bump the “Throttled Requests” count.

Standard tier uses credit-based throttling
- Each namespace gets 1,000 credits per second
- Data ops (Send/Receive/Peek) cost 1 credit each
- Management ops (Create/Update/Delete entities) cost 10 credits each
- Filter evaluations on topics cost 1 credit per filter
When credits run out within that one-second window, additional calls return a 50009 (“entity is being throttled”) and Azure Monitor logs those as Throttled Requests.
You’ll see the Throttled Requests metric under the “Service Bus – Request” namespace in Azure Monitor, regardless of whether you’re on Standard or Premium.
Typical scenarios that cause throttling in Standard:
- Bursts of message send/receive operations that push you over 1,000 credits/sec
- Lots of management-plane operations (creating/deleting queues or rules)
- Heavy topic‐filter evaluation when publishing messages

References:

Hope this helps!

If the resolution was helpful, kindly take a moment to click on User's image and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-05-25T15:12:59.55+00:00

@Wang Meihua , Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.

1 additional answer

Your answer

Pravallika KV 18,850 Reputation points Microsoft External Staff Moderator

2026-05-25T15:12:59.55+00:00

@Wang Meihua , Following up to see if the provided answer was helpful. If this answers your query, do click Accept Answer =>Yes, and upvote it. If you have any further queries do let us know.

Answer 1

Yes, the Throttled Requests metric is available for both Standard and Premium Azure Service Bus tiers.

In Azure Monitor, Throttled Requests is one of the common request metrics for Service Bus namespaces. It is defined as:

“The number of requests that were throttled because the usage was exceeded.”

For Standard tier, throttling occurs because it uses shared resources. When a single namespace or workload exceeds its fair-share limits on those shared resources, Service Bus starts throttling requests from that namespace so other tenants sharing the same infrastructure are not impacted. Typical scenarios include:

High request rate (send/receive/management operations) that exceeds the allowed throughput for the Standard tier.
Spikes in traffic where a single workload temporarily consumes more than its fair share of shared capacity.

When this happens:

The client receives a throttling error such as:

  The request was terminated because the entity is being throttled. Error code: 50009. Please wait 2 seconds and try again.

The corresponding operations are counted in the Throttled Requests metric in Azure Monitor.
SDKs and other Azure PaaS offerings rely on built-in retry policies with exponential backoff so throttled requests are retried and eventually succeed once credits are replenished.

If the application is sensitive to throttling, migrating the namespace from Standard to Premium is recommended so that dedicated resources can be allocated and scaled to reduce the likelihood of throttling.

References: