rigetti / rigetti/qcs-sdk-rust
Improve Otel context extraction failure behavior
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
When https://github.com/rigetti/pyo3-opentelemetry/issues/27 is resolved, create a callback to handle OTel context extraction failure.
My current persuasion is that the error should be traced using the tracing package. Some downstream applications execute and translate at a high rate. Context extraction failures may be due to the fact the Python side does not have opentelemetry package installed. We don't want to spam stderr. I suggest we make this a tracing::debug! event.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the linked pyo3-opentelemetry issue 27, then locate the current OTel context extraction path in qcs-sdk-rust. Determine the callback behavior for extraction failures and verify that failures are reported through tracing at debug level without writing to stderr.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100