Skip to main content

metrics.update-dora

Type: commands | Track: Enterprise

Autonomously collect DORA metrics per product from version control history. Local-first — works offline with zero cloud dependencies. Cloud enrichment optional via GitHub CLI. Delegates to observability-engineer. Exempt from PO+CA coordination.


Quick Start

Invoke via ADLC command interface: /metrics:update-dora

Manual fallback: /metrics:update-dora --product runbooks --deploy-freq "14/month"


Schema

product,metric,value,target,band,period,updated,source


DORA Metrics Collected

MetricSourceDescription
Deployment Frequency (DF)Version tagsReleases per month from release tags
Lead Time (LT)Commit-to-tag deltaHours from first commit to release tag
Change Failure Rate (CFR)Fix commits / totalPercentage of deployments requiring hotfix
Mean Time to Restore (MTTR)Hotfix timestampsHours from failure detection to resolution

Benefits

  1. Local-first with zero cloud dependencies — works offline from version history
  2. Writes to docs/static/data/dora.csv — feeds the DORA dashboard and all ceremony outputs
  3. Exempt from PO+CA coordination — reads version history and existing CSV only
  4. Manual override available when version history is incomplete

When to Use

AttributeDetail
PersonaObservability Engineer (OE)
TriggerDORA metrics collection — daily at session start to keep the DORA CSV current, or at sprint end before the sprint review and retro ceremonies need up-to-date actuals
Business ValueAutomated version-history-based DORA metrics that feed all ceremony outputs — eliminates manual metric collection and ensures DORA actuals are always current for stakeholder reporting
FrequencyDaily / Sprint

Example: As an Observability Engineer, I need to update DORA metrics before the sprint review because the review template reads from dora.csv and stale metrics will produce an inaccurate sprint velocity report. I run /metrics:update-dora which calculates deployment frequency, lead time, change failure rate, and mean time to restore from version history, then writes updated values to docs/static/data/dora.csv for all tracked products.

Coordination-exempt command. Reads version history and existing CSV data only.