-
Notifications
You must be signed in to change notification settings - Fork 2.8k
datadog no resource serviceName #21525
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
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This is interesting, when you're looking through the UI. Do you see the |
I saw the issue as well with a similar setup. I was able to work around it with the following processor, but I'm not familiar enough with the data model to understand why this worked. Something to do with the service name being set in individual spans, but not the resource?
Edit: looks like there's another similar issue #21210 |
Yeah, I am just looking at creating a PR for it now but it will be a breaking change. |
Will be fixed in the next release. |
Uh oh!
There was an error while loading. Please reload this page.
Component(s)
receiver/datadog
What happened?
Description
Currently in addResourceData
service.name
is not set. Its set in the span attributes. Because of this traces exported to backends like jaeger are appearing asempty-service-name
Steps to Reproduce
https://github.com/DataDog/dd-trace-php set env[DD_SERVICE] = my-app
Expected Result
jaeger ui service name is my-app
Actual Result
jaeger ui service name is empty-service-name

Collector version
v0.76.1
Environment information
Environment
OS: Ubuntu 20.04
OpenTelemetry Collector configuration
Log output
No response
Additional context
[receiver/datadog] not set at trace resource resulting in OTLPResourceNoServiceName
The text was updated successfully, but these errors were encountered: