oxidecomputer / oxidecomputer/omicron
Alerts should have more granular scoping than "fleet"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Currently, alerts are hard-coded to only be visible in the fleet scope, meaning that fleet operators see them.
But there are many conditions whereby a user within a silo would want access to alerts.
These include:
- Monitoring an instance for state changes (seems reasonable for a regular silo user)
- Notifications upon silo cert expiration (for silo admins, see: https://github.com/oxidecomputer/omicron/pull/11238)
This granularity could likely continue beyond silos, to individual project levels.
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 how alerts are currently limited to the fleet scope, then read the linked pull request 11238 for the silo certificate-expiration context. Define which alert scopes should be supported for fleet, silo, and project users, along with the access rules and completion criteria; the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100