oxidecomputer / oxidecomputer/omicron
wicket should log individual component update ids
Open
Beginner friendly
Nobody has claimed this yet.
Debugging
Update System
wicket
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently wicket will log the mupdate id, e.g. the UUID for an overall update, but not the id generated for each component update.
This makes correlating the state of an update between wicket and MGS logs difficult. We should log the component update id as well.
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 in wicketd/src/update_tracker.rs around line 2780, where the component update id is generated. Trace the existing logging for the overall mupdate id and update it so each component update id is also emitted. Done means wicket logs contain the component update ids needed to correlate state with MGS logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100