Bug (?): Can't monitor an external Postgres managed database

Hey! I'm trying to monitor a DigitalOcean managed Postgres with Coroot, and I can't find any way to do it.

The DB shows up only as an ExternalService. It never gets classified as postgres (traffic is TLS, so I guess the protocol can't be sniffed), so the Postgres instrumentation form never appears. And there's no field anywhere to just type in a host + credentials.

Digging into the code, it looks like the host for instrumentation is always taken from an observed TCP listen socket on a monitored instance, and the settings model has no Host field. A managed DB runs on DigitalOcean's side (25060, 25061 (conn pool), so it has no local listen socket — meaning no target is ever created.

The old coroot-pg-agent was a nice workaround (it connects out via a DSN), but it got archived a week ago. It still works, but it's unmaintained now.

Would be great to have a supported way to point Coroot at an external DB — e.g. an optional host field in the instrumentation settings, or letting me set the type on an external service.

Thanks!