quickwit-oss / quickwit-oss/quickwit
Use tags and service name to derive a process ID in the jaeger REST API
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
We added in #4197 Jaeger REST endpoints.
The code logic used to convert gRPC objects into the REST ones has a missing part. During the conversion, we build process IDs from the service name, we should also take into account tags to build those IDs, ref
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 in quickwit/quickwit-serve/src/jaeger_api/model.rs near the process ID conversion referenced in the issue. Trace how gRPC objects become REST models and confirm how service names and tags should contribute to process IDs; done means the derived IDs include the relevant tags and the Jaeger REST response remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend, observability-sre
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100