-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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] Remove service
setting
#8781
Labels
exporter/datadog
Datadog components
Comments
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What will change?
The
service
setting from the Datadog exporter will be removed in favor of using theservice.name
semantic convention, which is a required convention.Who is affected?
You are affected if you use the
service
setting from the exporter. If you are affected, a warning will be logged stating that you are using it, together with a link to this issue.Example warning:
What should I do if I am affected?
Remove any references to
service
from your configuration and set theservice.name
semantic convention on your SDK or using the resource processor instead.Example using the Go SDK for traces (click to expand)
If using:
You can remove the
service
setting and set this as a resource on the Go SDK, as shown on the official example:First, create a new resource with the service name:
Then, pass it to your trace provider builder as an option:
All language SDKs support setting semantic conventions; if you need help please reach out on the language SDK repo or comment here
Example using the resource processor (click to expand)
If using:
You can replace it by using a
resource
processor, which will override any existingservice.name
attribute:Lastly, you need to add the resource processor to all your pipelines.
When will it change?
To be filled when this happens
service
The text was updated successfully, but these errors were encountered: