AMQP 1.0: log client-provided connection name (when available) after accepting a connection

[lukebakken]

Is your feature request related to a problem? Please describe.

AMQP 0.9.1 connections log the client-provided connection name when opened. AMQP 1.0 does not appear to do so:

2024-08-08 17:11:32.448194+00:00 [info] <0.827.0> accepting AMQP connection 172.19.0.1:34366 -> 172.19.0.2:5672
2024-08-08 17:11:32.472664+00:00 [debug] <0.827.0> User 'guest' authenticated successfully by backend rabbit_auth_backend_internal
2024-08-08 17:11:32.475182+00:00 [info] <0.827.0> AMQP 1.0 connection: user 'guest' authenticated and granted access to vhost '/'
2024-08-08 17:11:32.475288+00:00 [debug] <0.827.0> AMQP 1.0 connection.open frame: hostname = vhost:/, extracted vhost = /, idle-time-out = undefined
2024-08-08 17:11:32.479714+00:00 [debug] <0.827.0> AMQP 1.0 created session process <0.832.0> for channel number 0

In the above case, my test code did set the connection name:

I'm testing with a freshly running docker container that uses the pivotalrabbitmq/rabbitmq:main image.

Describe the solution you'd like

Log the client-provided connection name when established.

[michaelklishin]

Note that client-provided connection name wasn't a part of the AMQP 0-9-1 spec, it is a (connection capabilities/metadata-based) convention we have added on top.

So it might involve client library changes.

[lukebakken]

So it might involve client library changes.

A client-provided connection name already appears to be supported by our .NET and Java AMQP 1.0 clients 👍