Spans in `tracing` and `opentelemetry` do not talk to each other
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
FYI this will only create a span in tracing, and not opentelemetry, as the two do not currently talk to each other. That's fine for now, as we have only used OTLP tracing experimentally.
Originally posted by @divergentdave in https://github.com/divviup/divviup-api/pull/2278#discussion_r3312486559
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
The issue provides no file, test, entry point, or requested change. Start by reviewing the referenced discussion in pull request 2278 to determine the intended relationship between tracing and opentelemetry; the current issue does not define what completion would look like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100