envoyproxy/envoy

Add the route name to trace data

Open

#21,605 opened on Jun 7, 2022

View on GitHub
 (1 comment) (0 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

Title: Add the route name to trace data

Description:

I would like to group and filter traces by route name, since that will be a key dimension for us; right now there's no good way of doing it. The route name is available in the access logs, but we sample those heavily and mostly rely on traces, which integrate much better with the rest of our observability data.

Contributor guide

Research direction
Understand the current tracing implementation in Envoy, specifically how trace data is structured. Identify where route name information is available (e.g., in access logs or routing context) and propose a way to attach it to spans.
Tech stack
cpp
Domain
backend
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Envoy tracingOpenTelemetry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40