Add DORA band color thresholds and rolling trend panels #396
No reviewers
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-platform!396
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "395-dora-dashboard-band-color-thresholds-rol"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Updates the DORA Grafana dashboard with official performance band color thresholds on all 4 overview stat panels, and adds a new Trends row with 7d/30d rolling average timeseries panels for Deployment Frequency and Lead Time.
Changes
terraform/dashboards/dora-dashboard.jsonavg_over_time(...[7d:1d])avg_over_time(...[30d:1d])avg_over_time(...[7d:1d])avg_over_time(...[30d:1d])Test Plan
Review Checklist
Related Notes
None -- dashboard-only change, no docs impact.
Related
Closes #395
QA Review -- PR #396
Threshold Band Colors (DORA#4)
All four stat panels match the specified DORA performance band definitions.
Rolling Trend Panels (DORA#7)
[7d:1d][30d:1d][7d:1d][30d:1d]avg_over_time((<inner>)[Nd:1d])is correct for PrometheusStructural Checks
Findings
No issues found.
VERDICT: APPROVE
PR #396 Review
DOMAIN REVIEW
Tech Stack: Grafana JSON dashboard, Terraform-managed ConfigMap, PromQL queries.
Threshold Verification (Accelerate DORA bands):
PromQL Queries (Trend Panels):
avg_over_time((sum(rate(...))[Nd:1d])-- valid Prometheus subquery syntax.avg_over_time((histogram_quantile(0.5, ...))[Nd:1d])-- valid. Theby (le)aggregation inside histogram_quantile is correct.$repofilter, matching overview stat panel behavior (aggregate across all repos). Consistent.Grafana JSON Structure:
${DS_PROMETHEUS}variable. No hardcoded datasource references.BLOCKERS
None.
NITS
MTTR red threshold is more aggressive than DORA spec. MTTR red fires at >168h (1 week) but DORA "Low" is >1 month (720h). The 168h-720h range (1week to 1month) maps to the Medium-Low boundary in Accelerate. For a small team this is arguably better -- you want to see red sooner. But it means the MTTR thresholds don't exactly match the standard while the other three metrics do. Consider documenting this intentional deviation in a comment within the JSON, or adjusting to 720h for consistency.
Detail row thresholds not updated. The CFR gauge panel (id 11, line 338-344) and MTTR detail stat panel (id 13, line 392-398) still use the old color scheme (
orangeinstead ofblue, CFR red at 30 instead of 15). The overview and detail panels now show different color bands for the same metric. This is not in scope per the PR description ("all 4 overview stat panels"), but the inconsistency could confuse dashboard users. Consider a follow-up issue to align detail row thresholds.30d trend panels vs 15d retention. The PR body honestly documents that 30d panels will show partial data. This is fine, but consider adding a panel description or annotation in the Grafana JSON itself (the
descriptionfield on panels 16 and 18) so dashboard viewers see this caveat without reading the PR.No CFR/MTTR trend panels. Only DF and LT get trend panels. Issue #430 exists for "7d/30d rolling trend panels for DF and LT" specifically, so this is intentional. But consider noting in the PR body that CFR/MTTR trends are deferred so the scope boundary is explicit.
SOP COMPLIANCE
PROCESS OBSERVATIONS
VERDICT: APPROVED