marigold-dev / marigold-dev/deku
Infra: liveness/readiness probes
Open
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
From a infrastructure perspective it would be nice to have endpoints to query for the health of the deku node.
Either there can be 1 endpoint for everything or you can split it into 2
* liveness - the node is doing well and does not need to be restarted
* readiness - the node has started correctly
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or existing entry points. Start by locating the node's HTTP/API entry point and defining what liveness and readiness should verify; done means documented endpoint behavior and tests covering the selected health checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100