Repository navigation
feat(slos): SLO model, table and /v2/slos API - #2293
Conversation
An SLO targets one service's entry-point spans (optionally some environments), with an availability or latency SLI, a target percent and a 7/28/30 day window. Latency thresholds come from a fixed ladder the service rollups will count.
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 32 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
This comment has been minimized.
This comment has been minimized.
|
F1: valid on this PR alone. It's closed in part 4 (#2296): SLO create, update and delete take the per-org advisory lock ( Migration: |
Maple review🟢 Confidence 10/10 · safe to merge. Only F1 is left: the duplicate-name race still answers 503, deferred to #2296; tenancy filters and CRUD are pinned by the PGlite route tests. Adds the
Before merge
Still open from earlier reviews
Production impactOpen errors in the changed files (1)
After this merges, Maple checks whether they stop.
|
|
Merged with 1 step from "Before merge" still open. If it is done, tick it on the review comment; if not, now is the time.
|
Maple: after this shipped✅ Shipped clean. Nothing this change touches got worse in the hour after it deployed. Deployed to Errors in the changed files:
Maple looks once, an hour after the first deploy that carries the merge. |
Stack: #2293 model, #2294 latency ladder, #2295 compute, #2296 burn alerts, #2297 MCP, #2298 UI
Part 1 of 6 of SLOs with multiwindow burn-rate alerts.
An SLO targets one service's entry-point spans (the spans the service overview counts), optionally limited to some environments. It has:
availability(good = notError) orlatency(good = faster than a threshold from a fixed ladder, 50 ms to 10 s);What this PR adds:
slostable and its migration.SlosService, and/v2/sloswith list, create, retrieve, update and delete.slo_…public ids and audit actions.alerts:manage, because every SLO owns a burn-rate alert rule (part 4).Verification
slos:read/slos:writescopes.parity.test.ts, the OpenAPI paths list, anticipated errors and the org-scoped tables test all pass.🤖 Generated with Claude Code