mlabs-haskell / mlabs-haskell/congested-testnet
Uptime reports
Open
Nobody has claimed this yet.
- Dominant language
- Dhall
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We need to be able to provide evidence that the testnet has been up and running with at least 99% uptime.
Acceptance Criteria
- The report/dashboard is publicly accessible
- Granular history for the current day is shown
- Average uptime for at least the last 6 months can be viewed
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are named. Start by identifying how the testnet is deployed and currently monitored, then determine where a public report or dashboard can expose uptime history. Done means a public view shows granular current-day history and average uptime for at least six months, meeting the 99% evidence requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100