envoyproxy/envoy

tracing: support multiple providers

Open

#25,347 opened on Feb 3, 2023

View on GitHub
 (1 comment) (11 reactions) (0 assignees)C++ (5,373 forks)batch import
area/tracingenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

To support migration from one sink to another, it would be good to support multiple tracing providers simultaneously. For example, users may want to test out OTel first before turning off zipkin.

Contributor guide

Research direction
Investigate the current tracing provider registration mechanism and extend it to support multiple simultaneous providers, allowing gradual migration from one to another.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoytracing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30