search

open-telemetry / opentelemetry-collector-contrib

Contrib repository for the OpenTelemetry Collector
https://opentelemetry.io
Apache License 2.0
2.97k stars 2.3k forks source link

[receiver/datadog] Grafana Cloud Operations table is not detailed by endpoint #31938

Open ffapitalle opened 6 months ago

ffapitalle commented 6 months ago

Component(s)

receiver/datadog

Describe the issue you're reporting

Context

Having the following scenario

 +-------+           +---------+         +-------+         +--------------+
 | App A |     ->    | DD Agent |  ->   | OTelcol |   ->   | Grafana Cloud |
 +-------+           +---------+         +-------+         +--------------+

where

Issue

In Applications > Services > Operations table in Grafana Cloud, a detailed view of each request resources shows a consolidated view of all endpoints under an operation type entry, instead of a detailed list of endpoints or resources.

image

The official documentation states that the resources are derived from the span_name field in each trace.

It seems that the span is translated and the endpoint is added in a span attribute.

Is there a way to achieve the detailed view using this schema ?

BTW: Having the same app natively OTel instrumented yields the desired result, as seen below

image

github-actions[bot] commented 6 months ago

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

atoulme commented 6 months ago

Your image links are broken, would you please upload them again?

ffapitalle commented 6 months ago

Your image links are broken, would you please upload them again?

Done ! Let me know if they're fixed now.

jpkrohling commented 5 months ago

cc @cedricziel

github-actions[bot] commented 3 months ago

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

cedricziel commented 3 months ago

@ffapitalle can you attach a (few) span(s) that was forwarded to cloud? I want to understand what other attributes we could use to rewrite the span name. Ideally we'd evolve and use an equivalent to http.route etc

github-actions[bot] commented 1 month ago

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

atoulme commented 4 days ago

Code owners @boostchicken @gouthamve @jpkrohling @MovieStoreGuy please review.