Async Eventhub Consumer with Pyamqp: Link Detached after long idle period Results in High "User Errors" volume

With azure-eventhub on pyamqp, long idle periods (over an hour) can end with the link detached ('connection was inactive for more than the allowed 300000 milliseconds') and the consumer silently stops receiving events, which also floods the metrics blade with User Errors. Raising idle_timeout doesn't fix it, it just delays the failure. The reporter's workaround was to switch back to uamqp for the consumer client (add uamqp to dependencies and use it as the transport) until the pyamqp-side fix lands. If your async EventHub consumers go quiet after idle periods on pyamqp, try uamqp as the transport.

Source: gh:Azure/azure-sdk-for-python#28996 (Azure Key Vault)

In gh:Azure/azure-sdk-for-python#28996, the issue was: - package: azure-eventhub - version: 5.11.1 - OS: Debian Container (kubernetes pod): python:3.11-slim-bullseye - Python version: 3.11.2 Describe the bug Long idle periods (greater than 1 hour) sometimes result in very high volume of "User Errors" reported in the metrics blade for our Eventhub. These high "User Error" volumes are correlated with our Consumer Clients not receiving events after idle period has ended and Producers have started publishing events again.. The verified answer: With azure-eventhub on pyamqp, long idle periods (over an hour) can end with the link detached ('connection was inactive for more than the allowed 300000 milliseconds') and the consumer silently stops receiving events, which also floods the metrics blade with User Errors. Raising idle_timeout doesn't fix it, it just delays the failure. The reporter's workaround was to switch back to uamqp for the consumer client (add uamqp to dependencies and use it as the transport) until the pyamqp-side fix lands.. Issue URL: https://github.com/Azure/azure-sdk-for-python/issues/28996