vectordotdev/vector

New `azure_event_hubs` sink

Open

#2,434 opened on Apr 23, 2020

View on GitHub
 (12 comments) (9 reactions) (0 assignees)Rust (2,126 forks)batch import
domain: sinksgood first issuehave: shouldneeds: approvalprovider: azuresink: new

Repository metrics

Stars
 (21,837 stars)
PR merge metrics
 (Avg merge 5d 12h) (85 merged PRs in 30d)

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

Research direction
Examine the existing Kafka sink implementation in Vector (likely in `src/sinks/kafka.rs`) to understand the pattern for wrapping. Then adapt it to use Azure Event Hubs client libraries, potentially leveraging the Azure SDK for Rust. Review the issue comments for additional context on requirements. Test with a sample Azure Event Hubs instance to ensure correct integration.
Tech stack
rust
Domain
backendclouddata
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Basic RustVector sink architectureAzure Event Hubs basicsExisting Kafka sink code
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60