This repository has been archived by the owner on Nov 7, 2022. It is now read-only.
Add support for specifying service name in config #602
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The datadog exporter will currently drop the service name which is specified in the spans. See #198 for more information.
This aligns the datadog exporter with jaeger, wavefront, and zipkin. They already have this option.
A better solution would be to add support for multiple services, as many of the other exporters have, but that is a bit over the level of contribution I can do at the moment.
I've tested this against a live datadog setup and the service name is correctly propagated and displayed in their UI.
If you are okay with this contribution I will update the docs accordingly 😊