Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
ffapitalle opened this issue Mar 25, 2024 · 8 comments

Comments

@ffapitalle
Copy link

ffapitalle commented Mar 25, 2024

Component(s)

receiver/datadog

Describe the issue you're reporting

Context

Having the following scenario

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

where

  • Application A is a Datadog instrumented application
  • DD agent sends telemetry and traces to an additional endpoint
  • OTel collector is using Datadog's receiver
  • Data is ingested into Grafana Cloud using OTLP.

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

@ffapitalle ffapitalle added the needs triage New item requiring triage label Mar 25, 2024
Copy link
Contributor

Pinging code owners:

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

@atoulme
Copy link
Contributor

atoulme commented Mar 30, 2024

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

@ffapitalle
Copy link
Author

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

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

@jpkrohling
Copy link
Member

cc @cedricziel

Copy link
Contributor

github-actions bot commented Jul 1, 2024

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.

@github-actions github-actions bot added the Stale label Jul 1, 2024
@cedricziel
Copy link
Contributor

@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

Copy link
Contributor

github-actions bot commented Sep 2, 2024

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
Copy link
Contributor

atoulme commented Oct 2, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants