temporalio / temporalio/sdk-rust
[Feature Request] Investigate supporting customized OpenTelemetry gRPC connections and logging connection failures
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 161
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 67
Description
Describe the solution you'd like
Users may not be notified when OTel gRPC connections are failing, and also some users may need to adjust gRPC TLS settings (ideally a general purpose "insecure" would be nice, but if that is not possible in ClientTlsConfig, I think just customizing the domain_name and ca_certificates may be enough).
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 by tracing the OpenTelemetry gRPC connection setup and the ClientTlsConfig usage. Check how connection failures are currently surfaced or logged, and determine which TLS settings can be customized. Done means failures are observable and the requested gRPC TLS options have clear supported behavior, with tests covering the changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- networking, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100