Skip to content

Conversation

@dyl10s
Copy link
Contributor

@dyl10s dyl10s commented Feb 11, 2026

Description

  • Updates README.md
    • Slightly nicer configuration options section
    • Add additional documentation about configuration options to README.md
    • Added feature gate section
    • Added known limitations section
  • Fixed test output being incorrect
  • Promoted logs/metrics/traces to beta

Link to tracking issue

Fixes #41661

@dyl10s dyl10s marked this pull request as ready for review February 11, 2026 22:10
@dyl10s dyl10s requested review from a team and atoulme as code owners February 11, 2026 22:10
@github-actions github-actions bot requested a review from cparkins February 11, 2026 22:10

This feature gate controls which Azure Event Hubs client library is used by the receiver. When enabled (the default), the receiver uses the official [Azure SDK for Go](https://github.com/Azure/azure-sdk-for-go) `azeventhubs` library. This library provides improved performance, better error handling, and is the recommended choice.

The feature gate is now stable and enabled by default. It will be removed in v0.144.0, after which the `azeventhubs` library will be the only supported option.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I remove this full section or just the explanation part? I am unaware of the process of what happens to a feature flag once it is in the stable state. Can the flag just be removed entirely from the code?

### Checkpoint Persistence

- Without a configured [storage extension], checkpoint state is stored only in memory. If the collector restarts, the receiver will resume from the latest offset, potentially missing messages or reprocessing already-consumed messages.
- When using storage, ensure the storage directory is persistent across restarts.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

storage can be redis or db based, so not sure the storage directory advice is necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[receiver/azureeventhub] Promote azureeventhubreceiver to beta

3 participants