A module-wise consolidated report (updated every hour?), to know if any of our backend APIs are down
贡献者指南
技术栈
python
领域
backendobservability
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Python basicsUnderstanding of JARVIS's module structureBasic knowledge of API monitoring
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
45
研究方向
The issue proposes a consolidated dashboard for monitoring backend API status. Start by exploring the repository structure to identify existing modules and their API endpoints (e.g., in the 'modules' directory). Review the current logic for handling API calls and any existing health check endpoints. Look at previous comments or PRs for context on desired metrics. A simple JSON endpoint could list module status and be consumed by a frontend, but the scope remains vague. Discuss with maintainers to clarify whether a built in dashboard or an external monitoring tool is preferred.
Status Dashboard · swapagarwal/JARVIS-on-Messenger#207 | Good First Issue
