Decouple trace context propagation functionality for gRPC into a separate library
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- grpc, java
- Domain
- distributed-systems, observability
Research direction
Start by reviewing the existing instrumentation/grpc-1.6/library and its GrpcTelemetry ClientInterceptor, then trace how the Spanner client would consume trace context propagation. Done means a stable, propagation-only library is defined and usable without adding the alpha gRPC instrumentation library or its possible semantic-convention breaking changes.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
We want to propagate trace context using W3 Trace Context header(traceparent) in gRPC requests made by using Spanner client library.
Currently https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/grpc-1.6/library provides GrpcTelemetry ClientInterceptor which can be used to intercept gRPC calls and add trace context headers in calls. The issue is that this library is in alpha version due to work going on semantic conventions.
We want to avoid adding alpha version library inside Spanner client library for trace context propagation as it may have breaking change in the future and instead use a stable one.
Describe the solution you'd like
Creating a stable library specific to only trace context propagation can solve the issue.
Describe alternatives you've considered
No response
Additional context
No response
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 214
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-telemetry/opentelemetry-java-instrumentation
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
open-telemetry/opentelemetry-java-instrumentation#19264 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement needs triage
open-telemetry/opentelemetry-java-instrumentation#20189 · 1 assignee ·
All issues in open-telemetry/opentelemetry-java-instrumentation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
spring-projects/spring-modulith#1895 ·