[azure logs] Add AMQP-over-Websockets and proxy support#16955
Merged
Conversation
Supports `amqp` and `websocket` options, and allow using proxy when the `websocket` transport is selected.
transport config option|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Contributor
Author
|
@lucabelluccini, this PR adds AMQP-over-WebSockets and proxy support to the Azure Logs integration. I've updated the docs, but I'm not entirely happy with how they turned out. I'd love your input on what users would expect to see here to find out that the integration now supports AMQP-over-WebSockets and proxying. |
🚀 Benchmarks reportTo see the full report comment with |
chemamartinez
approved these changes
Jan 14, 2026
Contributor
|
Thank you @zmoog ! I think we should highlight:
|
Contributor
lucabelluccini
left a comment
There was a problem hiding this comment.
I've left a comment to clarify the support for this.
Contributor
Author
On it! |
Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
Changes: - Clarify processor v2 is required for websockets and proxy - Clarify minimum set of EA version (I would add the min version in the docs) - Highlight outbound connections
Contributor
Author
|
@lucabelluccini, we updated the docs, please take a look when you have time. |
💚 Build Succeeded
History
cc @zmoog |
|
Package azure - 1.35.0 containing this change is available at https://epr.elastic.co/package/azure/1.35.0/ |
jakubgalecki0
pushed a commit
to jakubgalecki0/integrations
that referenced
this pull request
Feb 19, 2026
Add the new Event Hubs `transport` config option that supports `AMQP` and `AMQP-over-Websockets` protocols. The `AMQP-over-Websockets` protocol allows reaching Event Hubs on the 443 (HTTPS) port, making the integration available in network environment with restrictions. When `AMQP-over-Websockets` is selected, users can also route traffic through a proxy by setting the `HTTPS_PROXY` environment variable. The Event Hubs `transport` config option requires stack versions 8.19.10, 9.1.10 and 9.2.4.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Add the new Event Hubs
transportconfig option that supportsAMQPandAMQP-over-Websocketsprotocols.The
AMQP-over-Websocketsprotocol allows reaching Event Hubs on the 443 (HTTPS) port, making the integration available in network environment with restrictions. WhenAMQP-over-Websocketsis selected, users can also route traffic through a proxy by setting theHTTPS_PROXYenvironment variable.The Event Hubs
transportconfig option requires stack versions 8.19.10, 9.1.10 and 9.2.4.Checklist
changelog.ymlfile.I have verified that any added dashboard complies with Kibana's Dashboard good practicesHow to test this PR locally
Related issues
Screenshots
UI
Docs