oxidecomputer / oxidecomputer/v-api
Better instrumentation
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 5
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 59
Description
- Split all endpoint handlers in to
*_opfunctions with their logic in a*_innerfunction - Expand instrument attributes used in api_user to all other
*_opand*_innerfunctions
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 locating the endpoint handlers and the existing api_user instrumentation. Split each handler into a *_op function and a *_inner function, then extend the instrument attributes across all such functions; done means every endpoint follows this structure and carries the requested instrumentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, observability
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100