Registry API
Telemetry analytics
Adoption, drift frequency, rollout health, CI compliance, override hotspots and renderer failures.
These read the hourly and daily rollups; the aggregate operation computes them (the same job as wl admin aggregate).
Operations
| Request | What it does |
|---|---|
| GET /api/v1/telemetry/analytics/package-adoption | Package adoption metrics |
| GET /api/v1/telemetry/analytics/drift-frequency | Drift frequency by type |
| GET /api/v1/telemetry/analytics/rollout-health | Version adoption velocity |
| GET /api/v1/telemetry/analytics/ci-compliance | CI vs local command execution |
| GET /api/v1/telemetry/analytics/override-hotspots | Override hotspot files |
| GET /api/v1/telemetry/analytics/renderer-failures | Renderer failure rates by provider |
| POST /api/v1/telemetry/analytics/aggregate | Compute telemetry rollups |
Paths and summaries come from apps/api/openapi.json, which CI regenerates from the route definitions; this site checks its list against that file. Telemetry ingest accepts a workspace key without a user session; everything else needs a signed-in user.