-
Notifications
You must be signed in to change notification settings - Fork 375
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
Change default service_name
values Part 2
#2765
Conversation
service_name
values Part 2
02761f1
to
47a3bcf
Compare
47a3bcf
to
02761f1
Compare
a693525
to
7bcf3b0
Compare
…h 'origin' into zarir/service-name-integrations-part-two
…ub.com/DataDog/dd-trace-rb into zarir/service-name-integrations-part-two
… defined as service name
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 great, @zarirhamza!
Are there still missing integrations to come in a future PR, or this is basically it?
This is the final PR! If it could be merged, that would be perfect, thank you! |
Is there any context on the why in this change? The PR also doesn't link to the previous PR :( |
The previous PR is here - #2760 This is in preparation for an upcoming feature, still being worked on |
Process to change all default values for
service_names
per integration toDD_SERVICE
service_name
values based on span attribute schema version. If version is v0, the default stays as is, otherwise if it is version v1, the default changes toDD_SERVICE
settings_spec.rb
per integration that tests the switching of defaults between v0 and v1.peer.service
values behindv0
schema version only as there will be changes to the value based on version in the future.Affected integrations:
httpclient
,httprb
,mongodb
,mysql2
,pg
,presto
,racecar
,rack
,redis
,rest_client
,sequel