<observations>
Date: May 8, 2026
* 🟡 (12:19) Dashboard bug: all 18 widgets used `count()` on spans dataset, inflating metrics 100-700x. Root cause: `count()` counts every child span (db queries, cache lookups, HTTP calls) within each request; single `/resources/` request generates ~4,400 spans. Fix: switched all widgets to `count_unique(trace)` which counts distinct traces (one per actual HTTP request).
* 🟡 (12:19) Real traffic numbers (14d): 7 total requests — 3 resource provisions, 2 deep-link logins, 1 account request, 1 catalog poll. Previous dashboard was showing 25,609 (incorrect).
* 🟡 (12:19) Dashboard layout finalized: Row 0 = 6 KPI cards (AcctReq, Resources, Logins, Catalog, Upgrades, Removals) with count_unique(trace); Row 1-2 = Requests Over Time (trace count by endpoint) + Spans per Request (raw span count for perf); Row 3-4 = Latency p95 (view/dispatch spans) + Endpoint Detail table (traces, spans, p50); Row 5 = 6 tag-based KPI cards (Seer, Plan ↑↓, NewOrg, Linked, NewUser, Return) — will populate after deploy; Row 6-7 = Provisions by Service + Operations Breakdown (tag-based) — will populate after deploy
* 🟡 (12:19) Dashboard URL: https://sentry.sentry.io/dashboard/4510068/
* 🟡 (12:19) All 18 widget rebuild tasks completed: Row 0 KPIs, Row 1-2 time series, Row 3-4 latency + table, Row 5 tag-based KPIs, Row 6-7 breakdown charts, final data accuracy verification
</observations>