codeforpdx / codeforpdx/recordexpungPDX
Status page for OECI load times
Open
Nobody has claimed this yet.
devops
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 93
- Avg merge
- 8m
- Merged PRs (30d)
- 9
Description
I'm thinking a ping every 3 hours should strike the balance between providing meaningful information and not being a DOS.
Contributor guide
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
The issue proposes a status page for OECI load times and suggests pinging every three hours. Start by searching the repository for existing load-time monitoring, status-page, or ping integrations. Done requires a defined status-page scope and an agreed monitoring cadence, but the issue does not name files, tests, or an implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100