Delivery metrics

terragucci estate reads the audit trail (audit.jsonl) and each project’s index.json from your bucket. It writes the four DORA metrics for each project and the whole estate to dora.json beside estate.json and to the Delivery section of estate.html.

The metrics

Metric	terragucci counts	From
Deployment frequency	applied waves per week	apply entries with result applied in audit.jsonl
Lead time	the median time from a change’s first plan to its wave applied, split in three (below)	tf-plan rows in index.json, and the approval-requested, approval and apply entries in audit.jsonl
Change failure rate	failed applies, plus applied waves whose roots drifted within 7 days, over all applies	apply entries with result failed, and tf-drift rows that found drift
Time to restore	the median time from a failed apply to the next apply of those roots, and from drift found to the next drift check that found none	apply entries, and tf-drift rows

A refused wave is the gate working, so it is neither an apply nor a failure. Until its approval, a waiting wave is not an apply either.

Infrastructure ships less often than an application. The page shows frequency per project as a trend and never rates a project against DORA’s performance tiers.

The window

Every number covers the newest eight weeks (Monday to Sunday in UTC, current week included). Each week also has its own row, trend in dora.json, with the same counts for that week alone.

Lead time and its split

Lead time starts at the first plan. terragucci finds the plan of an applied wave by its commit, or by the wave’s digest: a tf-plan row lists each wave’s set digest and review digest (wave_digests), and a merge commit’s wave binds the same digest its pull request planned. The clock then starts at the first plan of that pull request.

Part	From	To
before the gate	the first plan	the wave asking for an approval; the apply when no gate held the wave
at the gate	the wave asking for an approval	the approval
after the gate	the approval	the wave applied

Without a plan in the index, an applied wave has no lead time. The page shows the median of the total and of each part, so the three parts need not add up to the total.

Change failures and restores

An applied wave counts as failed when its roots drift within 7 days and no later apply of those roots came first. A tf-drift row lists the roots that drifted (drifted_roots). Rows written before that field existed match any root of their project.

Event	Incident	Field
an apply fails	opens one for the roots it failed on
another failure of roots already failing	joins the open incident
an apply applies each of those roots again	closes the apply’s incident
the first drift check that finds drift	opens a drift incident, as the drift issue does	drift_since on the tf-drift row
the next drift check that finds none	closes it	drift_cleared on that row

Checks of the same commit share one row of the index, so each tf-drift row carries the open drift forward. restore.open counts the incidents still open.

Requirements

Record	Without it
audit.jsonl	no apply counts: deployments, lead time and failed applies are zero, and the page says so. Run terragucci audit before terragucci estate.
tf-plan rows in each index.json	no lead time
tf-drift rows	no drift counts as a failure or a restore

An index keeps its newest 500 rows. Plans and drift checks older than that drop out of the lead time and the drift counts; the audit trail keeps every apply.

dora.json

dora.json is terragucci.dora/v1, with its JSON Schema in the package as dist/dora.schema.json.

Field	What it holds
generated	when it was built
weeks, window	how many weeks it covers, and the first Monday and the end
drift_window_seconds	how soon after an apply drift counts against it
audit	whether audit.jsonl was read
estate	the metrics across every project
projects[]	each project’s metrics, with project

Each set of metrics holds:

Field	What it holds
deployments, per_week	applied waves in the window, and per week
lead_time	changes counted, median_seconds, and the split as before_gate_seconds, at_gate_seconds and after_gate_seconds; null when nothing counts
change_failure	applies, failed, drifted and rate; rate is null with no applies
restore	restored, open, median_seconds, and how many restores were of applies and of drift
trend[]	a row per week, oldest first: week, deployments, applies, failures, lead_time_seconds, restore_seconds

Gauges

With OTEL_EXPORTER_OTLP_ENDPOINT (or the metrics endpoint) set, terragucci estate sends one batch of gauges, labelled project. The estate’s own values carry project="*". The Estate dashboard graphs them in its Delivery row.

Gauge	Labels
terragucci_dora_deployments_per_week	project
terragucci_dora_lead_time_seconds	project, segment: total, before_gate, at_gate, after_gate
terragucci_dora_change_failure_ratio	project
terragucci_dora_restore_seconds	project

A metric with nothing to count, such as a lead time with no plan found, is not sent. Traces and metrics covers the collector and the dashboards.