envoyproxy/envoy

Enable setting trace operation to http path

Open

#31,134 opened on Nov 30, 2023

View on GitHub
 (5 comments) (2 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: Enable setting trace operation to http path

Description: Currently DataDog APM tracing for envoy is a really useful feature, the one downside though is that the operation name is hard coded in envoy to ether ingress or egress and thus datadog groups all the different request paths together and its hard to tell the different routes apart.

image

Can an option be added that appends the request http path to the operation name thus allowing the datadog trace extension to use that as the resource name and split the requests up for unique stats like the following:

image

Relevant Links: https://docs.datadoghq.com/tracing/services/resource_page/

A resource is a particular action for a given [service](https://docs.datadoghq.com/tracing/glossary/#services) (typically an individual endpoint or query). Read more about resources in [Getting Started with APM](https://docs.datadoghq.com/tracing/glossary/). For each resource, APM automatically generates a dashboard page covering:

Contributor guide

Research direction
Examine the DataDog tracing extension in Envoy to locate where the operation name is set to 'ingress' or 'egress'. Then design a configuration option to append the HTTP path to the operation name, ensuring it can be toggled via configuration.
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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 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 architectureDistributed tracing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45