Introduce ResilienceContext.OperationKey
#1380
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.
Details on the issue fix or feature implementation
This PR introduces
ResilienceContext.OperationKey
that can be assigned to eachResilienceContext
. It's immutable property that is specified at the time of theResilienceContext
creation:Operation key flows to telemetry and is included in logs and metrics. The main scenario is to distinguish the particular operation at call site and to improve the telemetry. It should have low cardinality.
This also fills the feature gap we had between Polly V7 and Polly V8.
Contributes to #1365
Confirm the following