quickwit-oss / quickwit-oss/quickwit
Explore whether we can support the Jaeger data source in Grafana without using Jaeger frontend as a proxy.
Open
Nobody has claimed this yet.
enhancement
tracing
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
That's how you setup a proxy Jaeger data source:
- id: 1
name: Jaeger
type: jaeger
typeName: Jaeger
access: proxy
url: http://jaeger:16686
isDefault: false
jsonData:
httpMethod: POST
readOnly: false
The idea would be to point directly to Quickwit with url: http://localhost:7280/jaeger
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 reviewing the shown Grafana Jaeger proxy configuration and the proposed Quickwit URL, http://localhost:7280/jaeger. Determine whether Quickwit can serve the Jaeger data-source requests directly and define the required compatibility scope; the issue is done when direct Grafana access works without the Jaeger frontend proxy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100