quickwit-oss / quickwit-oss/quickwit
Add a diagnostic screen in the UI to notify of major errors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Often quickwit does not work due to some obvious problem: unable to connect to metastore, no control plane, lack of indexer,
impossibility to connect to the storage, etc.
We usually log those errors properly... But these logs are sometimes hidden in a sea of logs and users are not always looking at them.
It could be useful to report those major errors in the UI, on a diagnostic screen, showing clearly what is working (source connectivity, etc.) and what is not.
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 surveying the existing UI and the logged failure paths for metastore, control plane, indexer, and storage connectivity. Define which major errors the diagnostic screen reports, how it shows working and failing components, and how users can verify the completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100