oxidecomputer / oxidecomputer/omicron
fm: want timeserieses for (approximate) size of sitreps
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
@smklein and i have been worrying a lot about sitreps getting "big" or taking "a long time" to load or insert, but we don't actually have a way of measuring this at present. Because sitrep insertion and loading are "lock free" and don't require any transactions, we don't get transaction duration metrics, and we aren't recording anything about how much JSON we're actually stuffing into the database. It's probably worth having a way to actually measure these things...
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
No files, tests, or entry points are named. Start by locating the sitrep insertion and loading paths and existing time-series or metrics instrumentation; clarify which approximate size and duration measurements are required, then consider the work done when those measurements are recorded and queryable for sitreps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100