open-telemetry / open-telemetry/opentelemetry-java
grpc-managed-channel sender ignores exporter RetryPolicy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 58
Description
Is your feature request related to a problem? Please describe.
We use opentelemetry-java in our platform and since https://github.com/open-telemetry/opentelemetry-java/pull/2995 all the services that start before the opentelemetry collector generate an ERROR log because the collector is not available yet:
https://github.com/open-telemetry/opentelemetry-java/blob/main/exporters/otlp/all/src/main/java/io/opentelemetry/exporter/otlp/internal/GrpcExporter.java#L100
Describe the solution you'd like
Describe alternatives you've considered
Additional context
We're using opentelemetry-java 1.63.0
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.
Research direction
Start at exporters/otlp/all/src/main/java/io/opentelemetry/exporter/otlp/internal/GrpcExporter.java around line 100, then trace how the grpc-managed-channel sender handles the exporter RetryPolicy. Define the expected behavior when the collector is unavailable and verify that startup no longer produces an ERROR log while retry policy behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java
- Domain
- networking, observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100