User Agent not showing

[Yuan325]

Bug Description

I added user agent to our alloydb Dialer, however, the user agent is not showing up on our dashboard. Through debugging it seems like it get parsed to the connector library.

Example code (or command)

opts := []alloydbconn.Option{alloydbconn.WithUserAgent(userAgent)}
d, err := alloydbconn.NewDialer(ctx, opts...)

Stacktrace

Steps to reproduce?

1. ?
2. ?
3. ?
   ...

Environment

1. OS type and version: n/a
2. Go version: 1.23.0
3. AlloyDB Go Connector version: v1.13.2

Additional Details

No response

[nancynh]

Hi @Yuan325, I wasn't able to reproduce your issue. I see from our backend logs that the UserAgent is propagated through correctly. Could you describe in a bit more detail how you're extracting the UserAgent and passing it to your dashboard? (or pinging me with details internally is also fine)

[nancynh]

Chatted with Yuan offline - it's not an issue with the Go connector since I was also able to see their custom user agent passed through from the Go connector to the Auth Proxy server based on the server logs on their instance. It's likely an issue with how they're getting this data.

[enocom]

Re-opening because we see a case where this isn't working as intended.

[enocom]

The generated client library we use to interact with the AlloyDB REST API eventually calls google.golang.org/api/transport/http.NewClient, which then reaches this code:

https://github.com/googleapis/google-api-go-client/blob/88e8ed9bd77df46f04da575ef89d94f7aa11f1e4/transport/http/dial.go#L101-L107

Note that the user agent isn't set, whereas it is in the other code path:

https://github.com/googleapis/google-api-go-client/blob/88e8ed9bd77df46f04da575ef89d94f7aa11f1e4/transport/http/dial.go#L164

[enocom]

This will be fixed when we pull in the yet to be released google.golang.org/api here: googleapis/google-api-go-client#3039.

[enocom]

v0.224.0 is out. We'll pull this in our own next release on Tuesday.

[enocom]

Fixed in #659.