-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/datadog] resource name renamed when http.method and http.route is defined? #25902
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@karmingc this is currently the expected behaviour for resource name.
The logic that extracts the resource name can be found here ( You can override this logic shared above by setting attribute |
Thanks for the insight @mackjmr. |
Component(s)
exporter/datadog
What happened?
Description
It seems like the resource name is replaced when
http.method
is defined.http.route
is appended if it exist instead of using the span name.edit: currently using this workaround: #1909 (comment)
Note: I am still looking where this is happening, so I am unsure if this is really an exporter issue. However, I added zipkin as an
exporter
and it doesn't seem to be the case there. I opened this ticket to get some pointers from somebody more knowledgeable of the codebase...Steps to Reproduce
http.method
andhttp.route
to the appropriate span.Expected Result
This should probably configurable and not default to those tags.
Actual Result
This currently defaults to the tags if they exist.
Collector version
0.81.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
With logging, I can't see the exported traces/spans. But with an error, I can see that resource is the provided
http.method
:Additional context
No response
The text was updated successfully, but these errors were encountered: