vectordotdev / vectordotdev/vector
New `azure_event_hubs` sink
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Azure Event Hubs is like a managed Kafka service:
Allow existing Apache Kafka clients and applications to talk to Event Hubs without any code changes—you get a managed Kafka experience without having to manage your own clusters.
This suggests that we could wrap the existing kafka sink. I'd prefer that we wrap it since it is technically a different service. We also get the marketing benefit (guides, ets) when we create a new sink.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing kafka sink and its configuration and registration paths, then confirm how Azure Event Hubs' Kafka compatibility affects the design. Done means a distinct azure_event_hubs sink wraps the existing Kafka sink behavior and has the associated guides or documentation described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, rust
- Domain
- cloud, stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100