Supabase support directed me to the egress discussion, which is locked. I would like to suggest more actionable information in egress warnings and usage reports.
My clipboard sync app was polling every five seconds and downloading its full history, including images already on the device. On November 13 it made 10,570 requests. We estimated about 90 GB of responses based on the compressed history size, close to the dashboard's 90.9 GB database API spike. That response total is an estimate, not a direct measurement. The detailed logs had expired by the time I investigated, so identifying the cause took longer. I have since changed the app to check item IDs and download only missing items.
It would help if an egress warning included:
I understand API gateway logs do not currently include response-byte data. Even a service-level breakdown, request counts by route, and a clear indication of which byte measurements are available would make the warning easier to act on. Thank you for considering this and for the grace period that gave me time to investigate and fix the app.
The user suggests improvements to egress warnings and usage reports to make them more actionable. They experienced a spike in database API usage due to their app's polling behavior and found it difficult to investigate due to expired logs. They propose adding more detailed information in warnings, such as time windows, service contributions, and route-specific data, to aid in quicker diagnosis.