Context
The legacy Event Hub SDK prevented us from offering Filebeat users the ability to connect to Event Hubs (and related Storage Account functionalities) using the corporate-friendly AMQP-over-WebSocket approach.
However, the modern Event Hubs SDK now supports the AMQP-over-WebSocket option.
Related issues:
Goal
Enable the azure-eventhub processor v2 to connect to Event Hubs via AMQP-over-WebSocket.
Impact
Opening the standard AMQP port (5672) is sometimes blocked by corporate firewalls, forcing users to rely on port 443. Implementing this feature removes a major deployment barrier for enterprise users.
Context
The legacy Event Hub SDK prevented us from offering Filebeat users the ability to connect to Event Hubs (and related Storage Account functionalities) using the corporate-friendly AMQP-over-WebSocket approach.
However, the modern Event Hubs SDK now supports the AMQP-over-WebSocket option.
Related issues:
Goal
Enable the azure-eventhub processor v2 to connect to Event Hubs via AMQP-over-WebSocket.
Impact
Opening the standard AMQP port (5672) is sometimes blocked by corporate firewalls, forcing users to rely on port 443. Implementing this feature removes a major deployment barrier for enterprise users.