Skip to content

Commit 8eaadc5

Browse files
v-shilsv-shils
authored
Merge pull request #267102 from spelluru/patch-46
Namespace -> Event Grid namespace
2 parents e3c10fb + 1efdcde commit 8eaadc5

File tree

3 files changed

+21
-21
lines changed

3 files changed

+21
-21
lines changed

‎articles/event-grid/choose-right-tier.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Use this tier if any of the following statements is true:
2828
* You require HTTP communication rates greater than 5 MB/s for ingress and egress using pull delivery or push delivery. Event Grid currently supports up to 40 MB/s for ingress and 80 MB/s for egress for events published to namespace topics (HTTP). MQTT supports a throughput rate of 40 MB/s for publisher and subscriber clients.
2929
* You require CloudEvents retention of up to 7 days.
3030

31-
For more information, see quotas and limits for [namespaces](quotas-limits.md#namespace-resource-limits).
31+
For more information, see quotas and limits for [namespaces](quotas-limits.md#event-grid-namespace-resource-limits).
3232

3333
## Event Grid basic tier
3434

‎articles/event-grid/includes/limits.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -17,32 +17,32 @@ ms.custom: include file, ignite-2023
1717

1818
Event Grid offers a standard tier and basic tier. Event Grid standard tier enables pub-sub using MQTT broker functionality and pull-delivery of messages through the Event Grid namespace. Event Grid basic tier enables push delivery using Event Grid custom topics, Event Grid system topics, Event domains, and Event Grid partner topics. See [Choose the right Event Grid tier](../choose-right-tier.md). This article describes the quota and limits for both tiers.
1919

20-
## Namespace resource limits
20+
## Event Grid Namespace resource limits
2121

2222
[Azure Event Grid namespaces](../concepts-event-grid-namespaces.md#namespaces) is available in public preview and enables MQTT messaging, and HTTP pull delivery.
2323
The following limits apply to namespace resources in Azure Event Grid.
2424

2525
| Limit description | Limit |
2626
|----------------------------------------|-------|
27-
| Namespaces per Azure subscription | 50 |
28-
| Maximum throughput units per namespace | 40 |
29-
| IP Firewall rules per Namespace | 16 |
27+
| Event Grid namespaces per Azure subscription | 50 |
28+
| Maximum throughput units per Event Grid namespace | 40 |
29+
| IP Firewall rules per Event Grid namespace | 16 |
3030

31-
## MQTT limits in namespace
31+
## MQTT limits in Event Grid namespace
3232

3333
The following limits apply to MQTT in Azure Event Grid namespace resource.
3434

3535
| Limit description | Limit |
3636
|----------------------------------------------|-----------------------------------------------------------------------------------|
37-
| MQTT sessions per namespace | 10,000 per TU |
38-
| Sessions per namespace | 10,000 per TU |
39-
| Session Expiry Interval | 8 hours, [configurable on the namespace](../mqtt-support.md#maximum-session-expiry-interval-configuration)|
40-
| Inbound MQTT publish requests per namespace | 1,000 messages per second per TU |
41-
| Inbound MQTT bandwidth per namespace | 1 MB per second per TU |
37+
| MQTT sessions per Event Grid namespace | 10,000 per TU |
38+
| Sessions per Event Grid namespace | 10,000 per TU |
39+
| Session Expiry Interval | 8 hours, [configurable on the Event Grid namespace](../mqtt-support.md#maximum-session-expiry-interval-configuration)|
40+
| Inbound MQTT publish requests per Event Grid namespace | 1,000 messages per second per TU |
41+
| Inbound MQTT bandwidth per Event Grid namespace | 1 MB per second per TU |
4242
| Inbound MQTT publish requests per session | 100 messages per second |
4343
| Inbound MQTT bandwidth per session | 1 MB per second |
44-
| Outbound MQTT publish requests per namespace | 1,000 messages per second per TU |
45-
| Outbound MQTT bandwidth per namespace | 1 MB per second per TU |
44+
| Outbound MQTT publish requests per Event Grid namespace | 1,000 messages per second per TU |
45+
| Outbound MQTT bandwidth per Event Grid namespace | 1 MB per second per TU |
4646
| Outbound MQTT publish requests per session| 100 messages per second |
4747
| Outbound MQTT bandwidth per session | 1 MB per second |
4848
| Max message size | 512 KB |
@@ -57,29 +57,29 @@ The following limits apply to MQTT in Azure Event Grid namespace resource.
5757
| MQTTv5 authentication data size | 8 KB |
5858
| Maximum keep-alive interval | 1160 |
5959
| Topic filters per MQTT SUBSCRIBE packet | 10 |
60-
| Subscribe and unsubscribe requests per namespace | 200 requests per second |
60+
| Subscribe and unsubscribe requests per Event Grid namespace | 200 requests per second |
6161
| Subscribe and unsubscribe requests per session | 5 requests per second |
6262
| Subscriptions per MQTT session | 50 |
63-
| Subscriptions per namespace | 1 million |
64-
| Subscriptions per MQTT topic | Unlimited, as long as they don't exceed the limit for subscriptions per namespace or session|
63+
| Subscriptions per Event Grid namespace | 1 million |
64+
| Subscriptions per MQTT topic | Unlimited, as long as they don't exceed the limit for subscriptions per Event Grid namespace or session|
6565
| Registered client resources | 10,000 clients per TU |
6666
| CA certificates | 10 |
6767
| Client groups | 10 |
6868
| Topic spaces | 10 |
6969
| Topic templates | 10 per topic space |
7070
| Permission bindings | 100 |
7171

72-
## Events limits in namespace
72+
## Events limits in Event Grid namespace
7373

7474
The following limits apply to events in Azure Event Grid namespace resource.
7575

7676
| Limit description | Limit |
7777
|----------------------------------------------------------------------|------------------------------------------------------------------------------------|
78-
| Namespace topics | 100 per TU |
78+
| Event Grid namespace topics | 100 per TU |
7979
| Event ingress | 1,000 events per second or 1 MB per second per TU (whichever comes first) |
8080
| Event egress (push and pull APIs) | Up to 2,000 events per second or 2 MB per second per TU |
8181
| Event egress (acknowledge, release, reject, and renew lock APIs) | Up to 2,000 events per second or 2 MB per second per TU |
82-
| Maximum event retention on namespace topics | 7 days |
82+
| Maximum event retention on Event Grid namespace topics | 7 days |
8383
| Subscriptions per topic | 500 |
8484
| Maximum event size | 1 MB |
8585
| Batch size | 1 MB |

‎articles/event-grid/monitor-mqtt-delivery-reference.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ This article provides a reference of log and metric data collected to analyze th
4747
| Protocol | The protocol used in the operation. The available values include: <br><br>- MQTT3: MQTT v3.1.1 <br>- MQTT5: MQTT v5 <br>- MQTT3-WS: MQTT v3.1.1 over WebSocket <br>- MQTT5-WS: MQTT v5 over WebSocket
4848
| Result | Result of the operation. The available values include: <br><br>- Success <br>- ClientError <br>- ServiceError |
4949
| Error | Error occurred during the operation.<br> The available values for MQTT: RequestCount, MQTT: Failed Published Messages, MQTT: Failed Subscription Operations metrics include: <br><br>-QuotaExceeded: the client exceeded one or more of the throttling limits that resulted in a failure <br>- AuthenticationError: a failure because of any authentication reasons. <br>- AuthorizationError: a failure because of any authorization reasons.<br>- ClientError: the client sent a bad request or used one of the unsupported features that resulted in a failure. <br>- ServiceError: a failure because of an unexpected server error or for a server's operational reason. <br><br> [Learn more about how the supported MQTT features.](mqtt-support.md) <br><br>The available values for MQTT: Failed Routed Messages metric include: <br><br>-AuthenticationError: the EventGrid Data Sender role for the custom topic configured as the destination for MQTT routed messages was deleted. <br>-TopicNotFoundError: The custom topic that is configured to receive all the MQTT routed messages was deleted. <br>-TooManyRequests: the number of MQTT routed messages per second exceeds the limit of the destination (namespace topic or custom topic) for MQTT routed messages. <br>- ServiceError: a failure because of an unexpected server error or for a server's operational reason. <br><br> [Learn more about how the MQTT broker handles each of these routing errors.](mqtt-routing.md#mqtt-message-routing-behavior)|
50-
| ThrottleType | The type of throttle limit that got exceeded in the namespace. The available values include: <br>- InboundBandwidthPerNamespace <br>- InboundBandwidthPerConnection <br>- IncomingPublishPacketsPerNamespace <br>- IncomingPublishPacketsPerConnection <br>- OutboundPublishPacketsPerNamespace <br>- OutboundPublishPacketsPerConnection <br>- OutboundBandwidthPerNamespace <br>- OutboundBandwidthPerConnection <br>- SubscribeOperationsPerNamespace <br>- SubscribeOperationsPerConnection <br>- ConnectPacketsPerNamespace <br><br>[Learn more about the limits](quotas-limits.md#mqtt-limits-in-namespace). |
50+
| ThrottleType | The type of throttle limit that got exceeded in the namespace. The available values include: <br>- InboundBandwidthPerNamespace <br>- InboundBandwidthPerConnection <br>- IncomingPublishPacketsPerNamespace <br>- IncomingPublishPacketsPerConnection <br>- OutboundPublishPacketsPerNamespace <br>- OutboundPublishPacketsPerConnection <br>- OutboundBandwidthPerNamespace <br>- OutboundBandwidthPerConnection <br>- SubscribeOperationsPerNamespace <br>- SubscribeOperationsPerConnection <br>- ConnectPacketsPerNamespace <br><br>[Learn more about the limits](quotas-limits.md#mqtt-limits-in-event-grid-namespace). |
5151
| QoS | Quality of service level. The available values are: 0, 1. |
5252
| Direction | The direction of the operation. The available values are: <br><br>- Inbound: inbound throughput to Event Grid. <br>- Outbound: outbound throughput from Event Grid. |
5353
| DropReason | The reason a session was dropped. The available values include: <br><br>- SessionExpiry: a persistent session has expired. <br>- TransientSession: a non-persistent session has expired. <br>- SessionOverflow: a client didn't connect during the lifespan of the session to receive queued QOS1 messages until the queue reached its maximum limit. <br>- AuthorizationError: a session drop because of any authorization reasons.
@@ -268,4 +268,4 @@ Here are the columns of the `EventGridNamespaceFailedMqttSubscriptions` Log Anal
268268
See the following articles:
269269

270270
- [Monitor pull delivery reference](monitor-pull-reference.md).
271-
- [Monitor push delivery reference](monitor-push-reference.md).
271+
- [Monitor push delivery reference](monitor-push-reference.md).

0 commit comments

Comments
 (0)