Analytics overview

See drift trends across your fleet — breaking vs additive events, watch health, and CI gate pass rate. Live dashboards ship with CP-5.3; below is a static preview of the console experience.

Overview Breaking Watches CI gates
Changes detected
128
↑ 12% vs prior week
Breaking changes
7
↓ 3 from last week
Watches healthy
94%
42 of 45 OK
CI pass rate
91%
↑ 4% after preview → enforce

Preview only. Production analytics will aggregate change records from D1, portfolio status from GET /api/portfolio/status, and CI outcomes from coverage assert runs. Tabbed views (Breaking, Watches, CI) and export land in phase CP-5.3.

What each metric means

  • Changes detected — total classified diffs (breaking, warning, info) across all watches in the range.
  • Breaking changes — events that would fail a strict gate or block preflight under production-guard policy.
  • Watches healthy — share of watches with drift_status: ok on last successful check.
  • CI pass rate — share of coverage assert runs that passed in connected repos.

Observability & logs

Change history and per-check run logs will mirror searchable observability: filter by watch or severity, and webhook delivery status. Until CP-5 ships, use the console fleet table and portfolio overview API.

Acquisition funnel (CP-5.6)

First-party funnel micro-events (docs traffic, trial wizard, sign-up) use POST /api/funnel/events and a client beacon — see Funnel beacon. Product drift metrics above are separate from acquisition funnel rollups.

Next steps

  • Funnel beacon — ingest API and privacy rules
  • Demo console — explore sample drift data
  • Change records — breaking vs additive semantics
  • Portfolio overview API — bulk status today