[azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 by zmoog · Pull Request #47956 · elastic/beats

zmoog · 2025-12-08T07:11:01Z

Proposed commit message

Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2.

Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option.

In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy.

Checklist

My code follows the style guidelines of this project
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have made corresponding change to the default configuration files
I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

No disruptive user impact. The input still defaults to AMQP transport, and unless users switch to WS transport, the behavior is unchanged.

Author's Checklist

Test with an actual proxy
Update the documentation for AMQP-over-WebSocket
Update the documentation HTTPS proxy

How to test this PR locally

I used the following Filebeat config:

# x-pack/filebeat/filebeat.yml
filebeat.inputs:
- type: azure-eventhub
  enabled: true

  # Event Hub configuration
  eventhub: "${EVENTHUB_NAME}"
  connection_string: "${EVENTHUB_CONNECTION_STRING}"
  consumer_group: "${EVENTHUB_CONSUMER_GROUP}"

  # Azure Storage configuration for checkpointing
  storage_account: "${STORAGE_ACCOUNT}"
  storage_account_connection_string: "${STORAGE_ACCOUNT_CONNECTION_STRING}"

  # Optional settings
  processor_version: ${PROCESSOR_VERSION}
  migrate_checkpoint: ${MIGRATE_CHECKPOINT}
  transport: "${TRANSPORT}"

Here are a couple of vscode configuration to test the WebSocket-only and WebSocket with HTTPS proxy scenarios (make sure to replace the placeholders YOUR * GOES HERE with actual values).

WebSocket only

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Filebeat",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/x-pack/filebeat/main.go",
            "args": [
                "-e",
                "-v",
                "-d",
                "*",
                "--strict.perms=false",
                "--path.home",
                "${workspaceFolder}/x-pack/filebeat",
                "-E",
                "cloud.id=<YOUR CLOUD ID GOES HERE>",
                "-E",
                "cloud.auth=<YOUR USERNAME GOES HERE>:<YOUR PASSWORD GOES HERE>",
                "-E",
                "gc_percent=100",
                "-E",
                "setup.ilm.enabled=false",
                "-E",
                "setup.template.enabled=false",
                "-E",
                "output.elasticsearch.allow_older_versions=true"
            ],
            "env": {
                "EVENTHUB_NAME": "logs",
                "EVENTHUB_CONNECTION_STRING": "<YOUR EVENT HUB CONNECTION STRING GOES HERE>",
                "EVENTHUB_CONSUMER_GROUP": "$Default",
                "STORAGE_ACCOUNT": "<YOUR STORAGE ACCOUNT NAME GOES HERE>",
                "STORAGE_ACCOUNT_KEY": "<YOUR STORAGE ACCOUNT KEY GOES HERE>",
                "STORAGE_ACCOUNT_CONNECTION_STRING": "<YOUR STORAGE ACCOUNT CONNECTION STRING GOES HERE>",
                "PROCESSOR_VERSION": "v2",
                "MIGRATE_CHECKPOINT": "true",
                "TRANSPORT": "websocket"
            }
        }
    ]
}

WebSocket with HTTPS proxy

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch Filebeat",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/x-pack/filebeat/main.go",
            "args": [
                "-e",
                "-v",
                "-d",
                "*",
                "--strict.perms=false",
                "--path.home",
                "${workspaceFolder}/x-pack/filebeat",
                "-E",
                "cloud.id=<YOUR CLOUD ID GOES HERE>",
                "-E",
                "cloud.auth=<YOUR USERNAME GOES HERE>:<YOUR PASSWORD GOES HERE>",
                "-E",
                "gc_percent=100",
                "-E",
                "setup.ilm.enabled=false",
                "-E",
                "setup.template.enabled=false",
                "-E",
                "output.elasticsearch.allow_older_versions=true"
            ],
            "env": {
                "EVENTHUB_NAME": "logs",
                "EVENTHUB_CONNECTION_STRING": "<YOUR EVENT HUB CONNECTION STRING GOES HERE>",
                "EVENTHUB_CONSUMER_GROUP": "$Default",
                "STORAGE_ACCOUNT": "<YOUR STORAGE ACCOUNT NAME GOES HERE>",
                "STORAGE_ACCOUNT_KEY": "<YOUR STORAGE ACCOUNT KEY GOES HERE>",
                "STORAGE_ACCOUNT_CONNECTION_STRING": "<YOUR STORAGE ACCOUNT CONNECTION STRING GOES HERE>",
                "PROCESSOR_VERSION": "v2",
                "MIGRATE_CHECKPOINT": "true",
                "TRANSPORT": "websocket",
                "HTTP_PROXY": "http://127.0.0.1:9090",
                "HTTPS_PROXY": "http://127.0.0.1:9090"
            }
        }
    ]
}

To test the proxy support, I used mitmproxy, an interactive HTTPS proxy with request inspection:

# Install
brew install mitmproxy  # macOS
# or
pip install mitmproxy

# Run the proxy
mitmproxy -p 9090

Since the Azure services require using an HTTPS proxy, you also need to set up a certificate for mitmproxy. See https://docs.mitmproxy.org/stable/concepts/certificates/ fore more details.

The mitmproxy main view:

Upgrade to AMQP-over-WebSocket:

WebSocket details:

Event hub messages received using AMQP-over-websocket through the proxy:

Related issues

Use cases

github-actions · 2025-12-08T07:11:10Z

🤖 GitHub comments

Just comment with:

run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

mergify · 2025-12-08T07:11:44Z

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @zmoog? 🙏.
For such, you'll need to label your PR with:

The upcoming major version of the Elastic Stack
The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
backport-active-all is the label that automatically backports to all active branches.
backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

kaiyan-sheng

Overall it looks good!!

x-pack/filebeat/input/azureeventhub/config.go

x-pack/filebeat/input/azureeventhub/v2_input.go

elasticmachine · 2025-12-09T11:38:10Z

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

cmacknz

Approving go.mod changes

# Conflicts: # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

github-actions · 2025-12-17T00:04:00Z

@Mergifyio backport 8.19 9.1 9.2 9.3

mergify · 2025-12-17T00:04:25Z

backport 8.19 9.1 9.2 9.3

❌ No backport have been created

Details

#48119 [8.19](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 8.19 but encountered conflicts
#48120 [9.1](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 9.1 but encountered conflicts
#48121 [9.2](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 9.2 but encountered conflicts
Backport to branch 9.3 failed

GitHub error: Branch not found

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy.

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy.

…cessor v2 (#47956) (#48119) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>

…cessor v2 (#47956) (#48120) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

…cessor v2 (#47956) (#48121) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go Co-authored-by: Maurizio Branca <maurizio.branca@elastic.co>

lucabelluccini · 2026-01-06T18:21:25Z

Hello @zmoog
Can you confirm the HTTP Proxy support can be done only via env vars (so Elastic Agent users need to set it in the EA systemd/unit file), and they have to eventually use NOPROXY to make sure only EventHub traffic goes through the proxy?
Also, the prerequisite is using processor_version v2 in integrations. Can we get it documented in https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-eventhub and https://www.elastic.co/docs/reference/integrations/azure ?

zmoog · 2026-01-09T17:18:26Z

Hello @zmoog Can you confirm the HTTP Proxy support can be done only via env vars (so Elastic Agent users need to set it in the EA systemd/unit file), and they have to eventually use NOPROXY to make sure only EventHub traffic goes through the proxy?

I tested proxy support by setting the HTTPS_PROXY environment variable — see "WebSocket with HTTPS proxy" in the PR description for full environment variables used.

Also, the prerequisite is using processor_version v2 in integrations.

Yes, all new features are available on processor v2 only.

Can we get it documented in https://www.elastic.co/docs/reference/beats/filebeat/filebeat-input-azure-eventhub and https://www.elastic.co/docs/reference/integrations/azure ?

Yes, sorry, my bad.

The missing Beats docs are my fault. The integration docs are not there yet, but we'll update them once I'll add support for the transport option in a new integration release (probably early next week).

mergify · 2026-04-09T09:56:23Z

backport 8.19 9.1 9.2 9.3

✅ Backports have been created

Details

#50025 [8.19](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 8.19 but encountered conflicts

Cherry-pick of af5d23e has failed:

On branch mergify/bp/8.19/pr-47956
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit af5d23e75.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1765280088-azure-eventhub-v2-add-support-for-amqp-over-websocket-and-https-proxy.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	both modified:   x-pack/filebeat/input/azureeventhub/auth.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

#50026 [9.1](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 9.1
#50027 [9.2](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 9.2 but encountered conflicts

Cherry-pick of af5d23e has failed:

On branch mergify/bp/9.2/pr-47956
Your branch is up to date with 'origin/9.2'.

You are currently cherry-picking commit af5d23e75.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1765280088-azure-eventhub-v2-add-support-for-amqp-over-websocket-and-https-proxy.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   x-pack/filebeat/input/azureeventhub/auth.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

#50028 [9.3](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 has been created for branch 9.3 but encountered conflicts

Cherry-pick of af5d23e has failed:

On branch mergify/bp/9.3/pr-47956
Your branch is up to date with 'origin/9.3'.

You are currently cherry-picking commit af5d23e75.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1765280088-azure-eventhub-v2-add-support-for-amqp-over-websocket-and-https-proxy.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum
	both modified:   x-pack/filebeat/input/azureeventhub/auth.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # go.mod # go.sum # x-pack/filebeat/input/azureeventhub/auth.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e)

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # go.mod # x-pack/filebeat/input/azureeventhub/auth.go

…cessor v2 (#47956) Support for AMQP-over-WebSocket transport in the azure-eventhub processor v2. Enterprise users often need to comply with network restrictions, which means using AMQP may not be an option. In addition to AMQP-over-WebSocket support, this change allows users to run the azure-eventhub input behind an HTTPS proxy. (cherry picked from commit af5d23e) # Conflicts: # go.mod # go.sum # x-pack/filebeat/input/azureeventhub/auth.go

zmoog self-assigned this Dec 8, 2025

zmoog added Team:obs-ds-hosted-services Label for the Observability Hosted Services team input:azure-eventhub labels Dec 8, 2025

botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Dec 8, 2025

zmoog added the backport-active-all Automated backport with mergify to all the active branches label Dec 8, 2025

zmoog changed the title ~~[azure-eventhub] Add (AMQP-over-)WebSocket transport~~ [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 Dec 8, 2025

kaiyan-sheng reviewed Dec 8, 2025

View reviewed changes

x-pack/filebeat/input/azureeventhub/config.go Show resolved Hide resolved

x-pack/filebeat/input/azureeventhub/v2_input.go Show resolved Hide resolved

zmoog force-pushed the zmoog/amqp-over-websocket branch from da7a45f to 359cd69 Compare December 9, 2025 11:37

zmoog marked this pull request as ready for review December 9, 2025 11:38

zmoog requested review from a team as code owners December 9, 2025 11:38

cmacknz approved these changes Dec 9, 2025

View reviewed changes

kaiyan-sheng approved these changes Dec 16, 2025

View reviewed changes

zmoog force-pushed the zmoog/amqp-over-websocket branch from c6b56fe to 7e7f2f3 Compare December 16, 2025 17:09

zmoog added 7 commits December 16, 2025 23:12

Add (AMQP-over-)WebSocket transport

d216f57

# Conflicts: # x-pack/filebeat/input/azureeventhub/config.go # x-pack/filebeat/input/azureeventhub/v2_input.go

Fix import order

842d6c0

Update NOTICE.txt

7cbfc55

Add changelog entry

bebe1a6

Cleanup

dbc541c

Move transport setup in the consumer client builder

eab141a

Fix incomplete refactoring

92d4f4c

zmoog force-pushed the zmoog/amqp-over-websocket branch from aea539d to 92d4f4c Compare December 16, 2025 22:12

zmoog enabled auto-merge (squash) December 16, 2025 22:36

zmoog merged commit af5d23e into main Dec 17, 2025
212 checks passed

zmoog deleted the zmoog/amqp-over-websocket branch December 17, 2025 00:03

mergify bot mentioned this pull request Dec 17, 2025

[8.19](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #48119

Merged

9 tasks

mergify bot mentioned this pull request Dec 17, 2025

[9.1](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #48120

Merged

9 tasks

mergify bot mentioned this pull request Dec 17, 2025

[9.2](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #48121

Merged

9 tasks

mergify bot mentioned this pull request Apr 9, 2026

[8.19](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #50025

Closed

9 tasks

mergify bot mentioned this pull request Apr 9, 2026

[9.1](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #50026

Closed

9 tasks

mergify bot mentioned this pull request Apr 9, 2026

[9.2](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #50027

Closed

9 tasks

mergify bot mentioned this pull request Apr 9, 2026

[9.3](backport #47956) [azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2 #50028

Closed

9 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2#47956

[azure-eventhub] Support for AMQP-over-WebSocket transport in the processor v2#47956
zmoog merged 7 commits intomainfrom
zmoog/amqp-over-websocket

zmoog commented Dec 8, 2025 •

edited

Loading

Uh oh!

github-actions bot commented Dec 8, 2025

Uh oh!

mergify bot commented Dec 8, 2025

Uh oh!

kaiyan-sheng left a comment

Uh oh!

Uh oh!

Uh oh!

elasticmachine commented Dec 9, 2025

Uh oh!

cmacknz left a comment

Uh oh!

Uh oh!

github-actions bot commented Dec 17, 2025

Uh oh!

mergify bot commented Dec 17, 2025 •

edited

Loading

Uh oh!

lucabelluccini commented Jan 6, 2026 •

edited

Loading

Uh oh!

zmoog commented Jan 9, 2026

Uh oh!

mergify bot commented Apr 9, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

zmoog commented Dec 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed commit message

Checklist

Disruptive User Impact

Author's Checklist

How to test this PR locally

Related issues

Use cases

Uh oh!

github-actions bot commented Dec 8, 2025

🤖 GitHub comments

Uh oh!

mergify bot commented Dec 8, 2025

Uh oh!

kaiyan-sheng left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

elasticmachine commented Dec 9, 2025

Uh oh!

cmacknz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions bot commented Dec 17, 2025

Uh oh!

mergify bot commented Dec 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ No backport have been created

Uh oh!

lucabelluccini commented Jan 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zmoog commented Jan 9, 2026

Uh oh!

mergify bot commented Apr 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Backports have been created

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

zmoog commented Dec 8, 2025 •

edited

Loading

mergify bot commented Dec 17, 2025 •

edited

Loading

lucabelluccini commented Jan 6, 2026 •

edited

Loading

mergify bot commented Apr 9, 2026 •

edited

Loading