grafana/pyroscope

UI should show better error when connecting to UI at wrong components

Open

#2,748 建立於 2023年11月22日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)C (9,041 star) (528 fork)batch import
frontendgood first issuehelp wanted

描述

Currently when opening the UI in micro-services mode and you pick a component that is not a querier or query-frontend, we show 405 errors (as the local query APIs are unavailable). Instead we should direct the user to connect to the query-frontend instead.

The only useful UI functions are probably the admin ones in this case

貢獻者指南

技術棧
javascripttypescriptreact
領域
frontend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic understanding of React componentsFamiliarity with error handling patterns
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Investigate the current error handling in the UI, particularly the API call that returns 405 errors. Look at the UI components responsible for displaying query errors, likely in the frontend directory. The improvement should detect when a user connects to a non query component and instead show a message directing them to the query frontend. Examine existing error handling logic in files like 'src/components/QueryError.jsx' or similar to understand the pattern.