2 comments (2 comments)0 reactions (0 reactions)0 assignees (0 assignees)Python1,284 stars (1,284 stars)972 forks (972 forks)batch import
Improvementhelp wanted
Description
A module-wise consolidated report (updated every hour?), to know if any of our backend APIs are down
Contributor guide
- Tech stack
- python
- Domain
- backendobservability
- Issue type
- feature
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 3
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-2 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- mostly clear
- Prerequisites
- Python basicsUnderstanding of JARVIS's module structureBasic knowledge of API monitoring
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 45
- Research direction
- 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.