-
Notifications
You must be signed in to change notification settings - Fork 458
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
internal/namingschema: add config flag to disable default integration service names #2007
internal/namingschema: add config flag to disable default integration service names #2007
Conversation
BenchmarksBenchmark execution time: 2023-06-14 09:57:04 Comparing candidate commit 8677744 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics. |
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.
LGTM
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.
lgtm
… service names (#2007) Co-authored-by: Andrew Glaude <andrew.glaude@datadoghq.com>
What does this PR do?
DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED
env variable andWithGlobalServiceName
tracer start option.Motivation
The motivation of this flag is to be able to to use the default service names introduced by the naming schema v1 (everything defaults to
DD_SERVICE
) while using naming schema v0 (so the operation names remain unchanged).AKA: This allows customers to upgrade to v1 SERVICE names while maintaining their V0 operation names. (Otherwise, V1 changes both service and operation names)
Describe how to test/QA your changes
Reviewer's Checklist