Skip to content

Remove client-specific retry attributes from server spans (per A72 tracing proposal) #8430

@vinothkumarr227

Description

@vinothkumarr227

Per the gRPC OpenTelemetry tracing proposal A72, retry information (e.g., previous-rpc-attempts, transparent-retry) is only tracked on the client side.

Currently, server spans incorrectly include client-specific retry attributes, which is not compliant with A72. This issue tracks the work required to remove these incorrect attributes and add appropriate unit tests.

Metadata

Metadata

Labels

Area: ObservabilityIncludes Stats, Tracing, Channelz, Healthz, Binlog, Reflection, Admin, GCP ObservabilityType: Bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions