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.