Modify log scope to use keyvalue pairs #32076
Merged
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.
Summary
The scopes example currently uses a plain string. This PR proposes to replace that with a KVP collection, containing the key "TransactionId". This matches the example use case that was described right above the example code snippet.
While Scope can accept any
object
includingstring
, most backends expect additional enrichments to come in the form of key-value pairs, so this is demonstrating a better practice of using Scopes.Fixes #Issue_Number (if available)