The per-route breakdown is exactly what's missing from the native dashboards. I've been running Trough for this: it sits in front of your HTTP API calls and tracks cost by route, so you can see "this endpoint is costing $X/day" rather than just an aggregate total. Retry storms show up as a spike on a specific route, which makes it easy to pinpoint the loop. Self-hosted Go binary, free for one service. stockyard.dev/trough
reply