feat: add connection property for enableEndToEndTracing #307
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
olavloite
approved these changes
Oct 18, 2024
olavloite
changed the title
Co-authored-by: Knut Olav Løite <[email protected]>
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.
By default, EndToEndTracing is disabled from backend.
This PR adds enableEndToEndTracing Boolean connection option for implementing opt-in feature for EndToEndTracing.
Example URL: cloudspanner:/projects/test-project-123/instances/test-instance-123/databases/test-database-123?enableEndToEndTracing=true
Note: You can also pass in enableEndToEndTracing=false, but that is the default behaviour (even if you do not pass in this option).