feat(process-tags): Propagate Service Naming Context via Process Tags#7762
feat(process-tags): Propagate Service Naming Context via Process Tags#7762pabloerhard merged 8 commits intomasterfrom
Conversation
Overall package sizeSelf size: 4.96 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.0.0 | 81.15 kB | 815.98 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7762 +/- ##
==========================================
+ Coverage 80.39% 80.44% +0.05%
==========================================
Files 741 741
Lines 32087 32170 +83
==========================================
+ Hits 25795 25878 +83
Misses 6292 6292
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
✨ Fix all issues with BitsAI or with Cursor
|
BenchmarksBenchmark execution time: 2026-03-12 16:32:16 Comparing candidate commit 204a5e1 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 233 metrics, 27 unstable metrics. |
amarziali
left a comment
There was a problem hiding this comment.
Looks good to me from a functional standpoint. Thanks
| if (config?.isServiceNameInferred) { | ||
| tags.push(['svc.auto', config.service]) | ||
| } else if (config) { | ||
| tags.push(['svc.user', true]) |
There was a problem hiding this comment.
If process tags are used for renaming services would it ever make sense to have a value of "true"?
There was a problem hiding this comment.
I'm not sure I get what you mean? From my understanding whenever the user actually did the naming of the service, we intend to not do any renaming.
…#7762) * initial work for service naming process tag * reworked process tags implementation * lint fix * removed testing leftovers * fix grammar mistake * fix test being undefined * added missing inits * debugger fix
…#7762) * initial work for service naming process tag * reworked process tags implementation * lint fix * removed testing leftovers * fix grammar mistake * fix test being undefined * added missing inits * debugger fix
What does this PR do?
This PR adds configuration dependent process tags, specifically svc.auto:<default_service_name> and svc.user.
Whenever a user sets the service name, we need to set a process tag indicating that. In this case, svc.user would be set to true. Whenever service name is inferred by the tracer, we should set svc.auto:<default_service_name>, with <default_service_name> replaced by the inferred service name.
Motivation
Additional Notes
Some modifications were required to add configuration dependent process tags to the processTags object, since it was originally a singleton that initialized itself at require time, which happened before config was built.