SpanOptions in RequestOptionsBase to create span for tracing#4655
Merged
ramya-rao-a merged 1 commit intoAzure:masterfrom Aug 5, 2019
Merged
SpanOptions in RequestOptionsBase to create span for tracing#4655ramya-rao-a merged 1 commit intoAzure:masterfrom
ramya-rao-a merged 1 commit intoAzure:masterfrom
Conversation
daviwil
approved these changes
Aug 5, 2019
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds a new property by the name
spanOptionstoRequestOptionsBaseincore-httpThis gets used to create new spans when tracing is enabled.
To keep #4654 restricted to Keyvault related changes, this change has been pulled out of that PR