Container health monitor
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.1k
- Forks
- 194
- Avg merge
- 18m
- Merged PRs (30d)
- 3
Description
Similar to #148 but for Docker containers.
I imagine two modes:
- Manual: Provide list of containers on a server to check the existence and health of. Fixed list of containers means alerts will fire either with failed healthchecks, or if they are not found—e.g.
docker compose down. - Auto: Check all containers on a server or servers, and match against whitelist/blacklist. Matched containers have their health checked. Allows any new containers that match the filter to be populated in the monitor automatically, while also removing old containers that no longer match/exist.
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
Start by reading issue #148 and comparing its monitor design with the two proposed Docker modes here. Define how fixed container lists, health-check failures, missing containers, and whitelist/blacklist matching should behave; the work is done when both manual and automatic monitoring requirements are implemented and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100