quickwit-oss / quickwit-oss/quickwit

Add an 'Open in Jaeger' option in quickwit-ui

Open
#3,738 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
11.7k
Forks
597
Avg merge
2d 22h
Merged PRs (30d)
37

Description

Is your feature request related to a problem? Please describe.
Using Quickwit I can quickly search logs and traces for relevant information. However, I would like to use Jaeger to look at the traces easily. While this can be done by manually copying the Trace ID and searching for it in Jaeger it would be nice if there was a shortcut.

Describe the solution you'd like
If Jaeger is enabled in Quickwit via configuration options, then the quickwit-ui could have a menu item on each log that would have an "Open in Jaeger" button in it. This would then utilize the configuration options to open the trace up in Jaeger to be viewed with.

Describe alternatives you've considered
One can always do this by hand. It's just a nice to have when debugging something. Using quickwit to search for problem spots and then other tools to further inspect things would be really helpful.

Additional context
Add any other context or information about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the quickwit-ui log-row or log-menu entry point and the existing Jaeger configuration options. Trace how a log's Trace ID is available in the UI and how configured Jaeger endpoints are represented; done means an enabled Jaeger setup exposes an "Open in Jaeger" action that opens the selected trace, while the option is absent or disabled when Jaeger is not configured.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.