-
Notifications
You must be signed in to change notification settings - Fork 369
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
Implement peer.service
and associated features
#2982
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2982 +/- ##
========================================
Coverage 98.09% 98.10%
========================================
Files 1305 1306 +1
Lines 72724 73244 +520
Branches 3360 3365 +5
========================================
+ Hits 71336 71853 +517
- Misses 1388 1391 +3
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
539cf20
to
9d0920f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to clarify that the requested changes are not about the SpanAttributeSchema
module discussion 😄 on #2982 (comment)
The request changes is about the missing specs on spec/datadog/core/configuration/option_spec.rb
and the addition of env_to_hash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zarirhamza and I talked about our plans for this. We identified there's a little more work to do to make peer.service
configurable. This should be in-flight; once its merged in to this branch, I think this will be ready.
As far as the code, it is LGTM. @zarirhamza, thanks for adding As for the |
…tags to each integration that implements them
be3cc20
to
a5a717e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thank you for all your hard work @zarirhamza!
peer.service
is now a tag that extracts its value from a subset of source tags that are unique per integration.Implement
peer.service
extraction logic in SpanAttributeSchema` Changepeer.service
logic #2953Replace
peer.service
tag in target integrations that create spans withspan.kind:client
orspan.kind:producer
over the oldpeer.service
tag that simply used to reflectspan.service
Implementpeer.service
#2943Remove all usages of
peer.service
from integrations that do not meet the above definition Implementpeer.service
#2943Implement remapper for
peer.service
that allows users to define key:value pairs which remap the value ofpeer.service
to a new remapped value Implementpeer.service
remapper #2958Add
DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED
so that users can enable global service name defaults toDD_SERVICE
AddsDD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED
#2907Needs explicit @delner approval