<observations>
Date: May 8, 2026
* 🟡 (12:04) Agent queried Snuba for Stripe Projects dashboard data — found "Accounts Linked" widget shows 0 because transaction name is `/remote/stripe-projects/provisioning/resources/` not `*account_requests*`
* 🟡 (12:05) Agent found most Stripe Projects transactions have `span.status:None` (not `ok`), so `span.status:ok` filter misses majority of data — 2582 of 3105 resources/ transactions have status=None in 7d window
* 🟡 (12:05) Agent discovered transaction URL names changed between 14d and 7d windows: 14d has `account_requests/` (8240) and `deep-link-login/` (3286); 7d has `resources/` (3105), `services/` (1581), `deep_links/` (714) — endpoint names were renamed/refactored
* 🟡 (12:06) Agent found `account_requests` traffic was a single burst: 8240 hits at 2026-04-29 15:00 UTC only
* 🟡 (12:06) Agent found `deep-link-login` traffic in two bursts: 1231 at 2026-04-29 07:00, 2055 at 2026-05-01 09:00
* 🟡 (12:07) Agent found `resources/` traffic in three bursts: 6406 at 2026-04-28 01:00, 2252 at 2026-04-28 22:00, 4650 at 2026-05-06 14:00; `services/` single burst: 775 at 2026-04-27 00:00
* 🟡 (12:07) Agent found Snuba data inconsistency: `deep_links/` returns 714 hits in 7d query but 0 in 14d query for exact same transaction name — suspected ClickHouse storage granularity or retention tier difference
* 🟡 (12:08) Agent identified traffic sources by IP/user: 4 IPs (52.37.153.176 — 9015 hits, 3.13.79.248 — 6406, 52.43.98.49 — 4650, 3.14.109.53 — 2252) and 2 authenticated users (id:3745827 — 2055 deep-link-login hits, id:4461305 — 1231 deep-link-login hits)
* 🟡 (12:08) Agent mapped IP-to-endpoint: ip:52.37.153.176 → account_requests (8240) + services (775); ip:3.13.79.248 → resources (6406); ip:52.43.98.49 → resources (4650); ip:3.14.109.53 → resources (2252); id:3745827 → deep-link-login (2055); id:4461305 → deep-link-login (1231)
* 🟡 (12:08) Agent found 1 log group in getsentry: `stripe_projects.spt.upgrade_failed` for ...