GraphQL: Instrument with GraphQL::Tracing::DataDogTrace
#3417
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TonyCTHsu
force-pushed
the
tonycthsu/new-graphql-tracer
branch
from
9559705
to
9ee02ee
Compare
TonyCTHsu
force-pushed
the
tonycthsu/new-graphql-tracer
branch
from
9ee02ee
to
1f55c23
Compare
marcotc
approved these changes
Jan 29, 2024
2 tasks
This was referenced Apr 12, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
2.0 Upgrade Guide notes
GraphQL instrumentation replace the deprecated
GraphQL::Tracing::DataDogTracingwithGraphQL::Tracing::DataDogTrace. An optionwith_deprecated_tracercan be configured if user want to continue usingGraphQL::Tracing::DataDogTracing. SinceGraphQL::Tracing::DataDogTraceis only available aftergraphql-ruby(>= 2.0.19), user prior to this version will fallback to the deprecatedGraphQL::Tracing::DataDogTracing