-
Notifications
You must be signed in to change notification settings - Fork 318
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
Peer service mapping #3320
Peer service mapping #3320
Conversation
Overall package sizeSelf size: 4.8 MB Dependency sizes
🤖 This report was automatically generated by heaviest-objects-in-the-universe |
BenchmarksBenchmark execution time: 2023-07-10 14:47:18 Comparing candidate commit 4a99565 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 469 metrics, 23 unstable metrics. |
8ba783e
to
54e897e
Compare
Codecov Report
@@ Coverage Diff @@
## master #3320 +/- ##
==========================================
+ Coverage 84.11% 84.21% +0.09%
==========================================
Files 204 204
Lines 8015 8020 +5
Branches 33 33
==========================================
+ Hits 6742 6754 +12
+ Misses 1273 1266 -7
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
188d745
to
bec2e9a
Compare
c02984e
to
3dd7fb1
Compare
3a98f56
to
689b4d0
Compare
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
689b4d0
to
4a99565
Compare
Can you also add this new environment variable to the documentation repo: Is this variable a standard across tracers? Such as Python? |
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
Supplying a `DD_TRACE_PEER_SERVICE_MAPPING` allows users to modify the `peer.service` tag in the same manner that `DD_SERVICE_MAPPING` does for service name. If the `peer.service` value was matched by the mapping, the original value of the tag before remapping is reported in `_dd.peer.service.remapped_from`.
What does this PR do?
Expose
DD_TRACE_PEER_SERVICE_MAPPING
, which behaves likeDD_SERVICE_MAPPING
, but for thepeer.service
tag.If the mapping is matched, the original value is reported in
_dd.peer.service.remapped_from
.Motivation
Plugin Checklist
Additional Notes