quickwit-oss / quickwit-oss/quickwit
Searching for a traceId in grafana / jaeger does not work after 3 days.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Describe the bug
Versions:
quickwit v0.8.2
Grafana v11.8.3
jaegertracing/jaeger-query:1.53.0
Datasources:
- 1 jaeger datasource against jaeger query
- 1 jaeger datasource against quickwit (
api/v1/otel-traces-v0_7/jaeger)
I make a search for a trace in grafana explore against a trace_id and I can see it. A few days later I cannot find the trace via the jaeger search (whereas I can still find it via the quickwit datasource).
I manually test trace Ids and I've isolated that traceIds fail to be searched (via jaeger) exactly after 3 days.
Expected behavior
I expect the trace to still be viewable via the quickwit viewer after a few days.
Configuration:
Please provide:
- Output of
quickwit --version - The index_config.yaml
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
Begin with the Grafana Explore trace_id search using the two listed Jaeger datasources and compare results before and after three days. Collect the requested quickwit --version output and index_config.yaml, then compare the Jaeger endpoint against the Quickwit datasource. Done means a trace remains searchable through the Jaeger datasource after three days.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, rust
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100