[otlp] Deserialize GrpcStatusDetailsHeader to Retrieve Grpc Retry Delay #5980
+631
−0
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.
Fixes Part of #5730
Design discussion issue #
Changes
Please provide a brief description of the changes here.
Introduces functionality to deserialize the
Google.Rpc.Status
proto from theGrpcStatusDetailsHeader(grpc-status-details-bin)
string and extract retry delay information from theGoogle.Rpc.RetryInfo
message embedded in theDetails
field.Deserialized proto: https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/Implementation/google/rpc/status.proto
Merge requirement checklist
CHANGELOG.md
files updated for non-trivial changes