envoyproxy/envoy

api: move configuration of tracer provider implementations out of `config.trace` into `extensions.tracers.<provider>`

Open

#10,737 opened on Apr 10, 2020

View on GitHub
 (6 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/configurationhelp wantedtech debt

Repository metrics

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

Description

Title: move configuration of tracer provider implementations out of config.trace into extensions.tracers.<provider>

Context:

  • proper placement of extension-specific configuration would have prevented #10576

Contributor guide

Research direction
Investigate the current tracer provider configuration location in config.trace and understand the extension configuration pattern to move it to extensions.tracers.<provider>.
Tech stack
cpp
Domain
backendapi
Issue type
Refactor
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.
Half day
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.
Needs investigation
Prerequisites
C++Envoy extension systemEnvoy configuration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25