-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[receiver/azureeventhub] Allow the Consumer Group to be set in Configuration #28633
Labels
Comments
cparkins
added
enhancement
New feature or request
needs triage
New item requiring triage
labels
Oct 25, 2023
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
djaglowski
pushed a commit
that referenced
this issue
Oct 26, 2023
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Allow the Consumer Group to be set in the Configuration. **Link to tracking Issue:** <Issue number if applicable> [#28633] **Testing:** <Describe what testing was performed and which tests were added.> Locally tested and verified. No unit testing added. **Documentation:** <Describe the documentation added.> New configuration option added to README.
Closed by #28634 |
sigilioso
pushed a commit
to carlossscastro/opentelemetry-collector-contrib
that referenced
this issue
Oct 27, 2023
…lemetry#28634) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Allow the Consumer Group to be set in the Configuration. **Link to tracking Issue:** <Issue number if applicable> [open-telemetry#28633] **Testing:** <Describe what testing was performed and which tests were added.> Locally tested and verified. No unit testing added. **Documentation:** <Describe the documentation added.> New configuration option added to README.
jmsnll
pushed a commit
to jmsnll/opentelemetry-collector-contrib
that referenced
this issue
Nov 12, 2023
…lemetry#28634) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Allow the Consumer Group to be set in the Configuration. **Link to tracking Issue:** <Issue number if applicable> [open-telemetry#28633] **Testing:** <Describe what testing was performed and which tests were added.> Locally tested and verified. No unit testing added. **Documentation:** <Describe the documentation added.> New configuration option added to README.
RoryCrispin
pushed a commit
to ClickHouse/opentelemetry-collector-contrib
that referenced
this issue
Nov 24, 2023
…lemetry#28634) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Allow the Consumer Group to be set in the Configuration. **Link to tracking Issue:** <Issue number if applicable> [open-telemetry#28633] **Testing:** <Describe what testing was performed and which tests were added.> Locally tested and verified. No unit testing added. **Documentation:** <Describe the documentation added.> New configuration option added to README.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/azureeventhub
Is your feature request related to a problem? Please describe.
Currently there is no way to configure the Consumer Group used when using the Event Hub Receiver. This feature is present in the Kafka Receiver and could be useful if another Client is already listening to the $Default Consumer Group.
Describe the solution you'd like
Allow the Consumer Group to be specified in the Configuration.
Describe alternatives you've considered
Using the Connection configuration to specify the Consumer Group (doesn't appear to be possible with the current library).
Additional context
This is an issue I ran into because of the described problem where an unidentified Client was connecting and consuming all messages. Which made it appear that no data was transiting the Event Hubs instance. This idea came up because I was trying to troubleshoot this issue, which was possible with the Kafka Receiver.
The text was updated successfully, but these errors were encountered: