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.
