-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Description
Component(s)
receiver/azureeventhub
What happened?
Description
Using the new feature flag / SDK with the Azure Event Hubs receiver, the consumer group no longer defaults to $Default if no consumer group is set. It should be a seamless update to the new SDK from the old one.
Steps to Reproduce
Run the collector with a simple pipeline using the new SDK feature flag
receiver.azureeventhubreceiver.UseAzeventhubs without the group config option set.
Expected Result
The collector successfully starts and begins collecting logs from Azure Event Hubs with the $Default consumer group
Actual Result
Error:
*Error{Condition: amqp:not-allowed, Description: null TrackingId:a73ebae6bb0643539890ffcb61f7b90b_G13, SystemTracker:gateway5, Timestamp:2025-09-29T13:31:46, Info: map[]}
Collector version
v0.136.0
Environment information
OpenTelemetry Collector configuration
receivers:
azureeventhub:
connection: "connection-string"
poll_rate: 1
format: "raw"
exporters:
file:
path: /tmp/azureeventhub_logs.txt
service:
# extensions: [file_storage]
pipelines:
logs:
receivers: [azureeventhub]
processors: []
exporters: [file]Log output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.