feat(uptime): monitor tree
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
env: server with some services
now:
server(ICMP) per 20s
serviceA(TCP) per 1min
serviceB(HTTP) per 1min
new:
server(ICMP) per 1min
├serviceA(TCP) per 1min
└serviceB(HTTP) per 1min
if A and B are down, server monitor change to per 20s.
if server is down, stop monitor A&B.
With logic like this, optimize the monitoring of stress and the number of notifications.
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 entry points are named. Start by locating the uptime monitoring scheduler and its server, TCP, and HTTP monitor handling; done means implementing the described tree-based cadence changes, stopping child checks when the server is down, and reducing unnecessary notifications.
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
- Mostly clear
- Newbie friendliness
- 25/100