Traces whose names contain no alphabetic characters are dropped about datadog-trace-agent HOT 4 CLOSED

Hi @aesy!

This is a very valid question and has been a long source of confusion in our APM product. While it is true that most tracing systems out there use a path for operation name, for Datadog it is different. In Datadog, the path of the operation is what we call "resource" and the operation name is similar (but not the same) to what is called "component". Some examples of good operation names: "http.request", "sql.query", etc.

While this may seem odd at first, it allows our product to have a unique set of capabilities provided through features such as Trace Search and percentile statistics. To most effectively benefit of these features it is recommended that the root span of a trace maintains the same name throughout requests.

This document illustrates a bit what best practices are but doesn't entirely cover the topic: https://docs.datadoghq.com/tracing/visualization/.

I hope this helps a bit. Happy to provide more insights if needed. Our (awesome) support team is also glad to help teach you more about these concepts and what best practices are.

from datadog-trace-agent.

Here is another article that could help:
https://help.datadoghq.com/hc/en-us/articles/115000702546-What-is-the-Difference-Between-Type-Service-Resource-and-Name-

from datadog-trace-agent.

Hi @gbbr,

Thanks a lot for the reply! I see I've misunderstood how datadog treats operation names. This seems to have caused other issues for me before without me realizing it. I went ahead and mapped the operation names of the root request span to 'http.request' and everything now work as expected.

I'm closing this as this no longer is an issue.

from datadog-trace-agent.

from datadog-trace-agent.