As a quick win to transparency for Managed Postgres (and reusing some elixir code from our dashboard, I’m not gonna lie to you
) we shipped a Logs UI so you can quickly follow what’s been happening with your database.
That being said, this is not quite there yet. You want logs to debug things and track what’s happening with your DB/App. Just streaming logs is not enough since it’s quite easy to miss what really happened at a specific point in time so expect more on the future for this!
Note
This UI required us to tweak some configs on postgres so it requires a restart to show all logs. If you have an existing cluster before this update you’ll see a CTA asking your permission to restart your cluster, but that’s just it. No existing data is affected.
It’s managed, baby
Don’t forget that this is managed postgres so feel free to not have to worry about logs and page us via support tickets UI or dedicated mail address if you feel something is off. We do already get automatically paged about any shenanigans your postgres go through though so you wont have to even worry about it.
![Manged Postgres Logs UI with multiple logs but a specific one is being expanded: "2025-09-10 13:46:09.579 UTC [44] LOG: checkpoint starting: force wait"](https://global.discourse-cdn.com/fly1/optimized/3X/6/f/6ffdcd83d96ccc90369616de5f93a762a3afc1e3_2_690x295.jpeg)