Merge pull request #77470 from spelluru/sbuslimit0521

No of calls to the GetRuntimeInfo method

Author: PRMerger16

articles/event-hubs/event-hubs-messaging-exceptions.md

@@ -89,6 +89,12 @@ This error can occur for one of two reasons:
 
 This error should rarely occur. It happens when the container running code for your namespace is low on CPU – not more than a few seconds before the Event Hubs load balancer begins.
 
+### Limit on calls to the GetRuntimeInformation method
+Azure Event Hubs supports up to 50 calls per second to the GetRuntimeInfo per second. You may receive an exception similar to the following one once the limit is reached:
+
+```
+ExceptionId: 00000000000-00000-0000-a48a-9c908fbe84f6-ServerBusyException: The request was terminated because the namespace 75248:aaa-default-eventhub-ns-prodb2b is being throttled. Error code : 50001. Please wait 10 seconds and try again.
+```
 
 ## Next steps
 

includes/event-hubs-limits.md

@@ -26,3 +26,4 @@ The following table lists quotas and limits specific to [Azure Event Hubs](https
 | Maximum retention period of event data |Entity |- |1-7 days |
 | Maximum throughput units |Namespace |Exceeding the throughput unit limit causes your data to be throttled and generates a [server busy exception](/dotnet/api/microsoft.servicebus.messaging.serverbusyexception). To request a larger number of throughput units for a Standard tier, file a [support request](/azure/azure-supportability/how-to-create-azure-support-request). [Additional throughput units](../articles/event-hubs/event-hubs-auto-inflate.md) are available in blocks of 20 on a committed purchase basis. |20 |
 | Number of authorization rules per namespace |Namespace|Subsequent requests for authorization rule creation are rejected.|12 |
+| Number of calls to the GetRuntimeInformation method | Entity | - | 50 per second |