envoyproxy / envoyproxy/envoy

Enable setting trace operation to http path

Open
#31,134 5 comments 2 reactions 0 assignees View on GitHub
area/tracing enhancement help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
437

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](https://github.com/envoyproxy/envoy/assets/126016798/95c1b12c-a884-4af6-b684-e9414c2de32e)

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](https://github.com/envoyproxy/envoy/assets/126016798/0096f040-8e24-4bf7-ad04-acda0684e303)

*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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.