Eno Compton

@pjain-sift What version are you using?

It's possible we've fixed this in the latest version (v1.17.1) which I'd recommend trying. The background certificate refresh will sometimes fail and if it does, its exception might appear in...

=== RUN TestRunConnectionCheck proxy_test.go:693: proxy.NewClient error: [proj.region.clust.inst1] Unable to mount socket: listen tcp 127.0.0.1:50002: bind: An attempt was made to access a socket in a way forbidden by its access...

Original issue: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/2372

Thanks, @gregdenton-google. I'm actively working on porting to OpenTelemetry, this time using system metrics instead of custom metrics. This requires a number of changes on the backend first and probably...

Some additional resources are here: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/issues/2477. Meanwhile, as of [v1.13.0](https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/releases/tag/v1.13.0) we have support for built-in metrics. Those metrics aren't public yet, but we're working on making them public.

``` java.util.concurrent.ExecutionException: com.google.cloud.sql.core.TerminalException: [***] The Google Cloud SQL Admin API failed for the project "***". Reason: Host "sqladmin.googleapis.com" not found ```

This is an interesting idea. Would this be for the Postgres protocol or for the raw bytes going back and forth?

More from the Postgres docs linked above. This is apparently an OpenSSL feature. > SSL compression is nowadays considered insecure and its use is no longer recommended. OpenSSL 1.1.0 disables...

We can port https://github.com/GoogleCloudPlatform/cloud-sql-python-connector/pull/1311 here.