SLO Burn Rate Monitoring UI

Module

Web

Status

VERIFIED

Description

SLO health dashboard with multi-window burn rate calculation (1h/6h/24h/72h Google SRE methodology), alert lifecycle management (fire/ack/resolve/snooze), error budget forecasting, and SLO CRUD.

Implementation Details

Feature directory: src/Web/StellaOps.Web/src/app/features/slo-monitoring/
Routes: slo.routes.ts
Components:
- slo-alert-list (src/Web/StellaOps.Web/src/app/features/slo-monitoring/slo-alert-list.component.ts)
- slo-dashboard (src/Web/StellaOps.Web/src/app/features/slo-monitoring/slo-dashboard.component.ts)
- slo-definitions (src/Web/StellaOps.Web/src/app/features/slo-monitoring/slo-definitions.component.ts)
- slo-detail (src/Web/StellaOps.Web/src/app/features/slo-monitoring/slo-detail.component.ts)
Source: SPRINT_20251229_031_FE_slo_burn_rate_monitoring

E2E Test Plan

Setup:
- Log in with a user that has appropriate permissions
- Navigate to /ops/jobengine/slo
- Ensure test data exists (scanned artifacts, SBOM data, or seed data as needed)
Core verification:
- Verify the component renders correctly with sample data
- Verify interactive elements respond to user input
- Verify data is fetched and displayed from the correct API endpoints
Edge cases:
- Verify graceful handling when backend API is unavailable (error state)
- Verify responsive layout at different viewport sizes
- Verify accessibility (keyboard navigation, screen reader labels, ARIA attributes)

Verification

Verified on 2026-02-11 via docs/qa/feature-checks/runs/web/slo-burn-rate-monitoring-ui/run-001/.
Tier 0 confirmed SLO route/component/client/model assets and key burn-rate/alert lifecycle symbols.
Tier 1 passed focused Angular behavior regression (14 files / 64 tests) and npm run build.
Tier 2 validated route coverage, client endpoint wiring for alert lifecycle and history windows, and dashboard/alert workflow behavior.

2.0 KiB Raw Blame History