liquidmetal-dev / liquidmetal-dev/flintlock
Add /debug endpoint to return useful stats about flintlock and microvms
Open
Nobody has claimed this yet.
kind/feature
lifecycle/stale
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 17h 24m
- Merged PRs (30d)
- 30
Description
To include specific info which is not in pprof
- mvm count
- interface count (and name?)
- etc add more
This is also a useful thing to have as like a test/ping endpoint to ensure the service is ready to receive requests.
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
Start by reviewing the existing pprof entry point and the service's request handling. Define the useful statistics to expose, including microVM and interface counts, and clarify the readiness response. Done means a /debug endpoint returns the agreed stats and can be used to verify that the service is ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100