Adding a few things that weren't covered yet, mostly around @smeubank point about people still seeing higher bills even with controls: 1. Let max switch itself back after a while, say 24h. People turn it up during an incident and forget, and the first they hear of it is the bill. That's probably where most of the surprise cost would come from once this ships. 2. Show what each level would cost before you switch, based on the last few days of traffic. Per-day usage tells you after the fact, an estimate lets people choose with the number in front of them. 3. For the 2xx sampling, keep full logs around errors. The successful requests right before a failure are often the ones you need, and those are what 1 in N sampling drops. If the last few minutes are held in a buffer and only written out when an error or slow request shows up, you get max-level detail around incidents for close to min cost.
Is it possible to retrieve the database credentials (connection string, password, etc.) for a preview branch that was created using the Supabase CLI with the "--with-data" flag? I’m asking because I’m trying to get the credentials for a branch where the data was copied over, but I’m unable to retrieve them through the CLI (supabase branches get) or the dashboard, without the admin resetting. We are trying to use that to auto provision the db in our worklow. Any insights or workarounds would be greatly appreciated