You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We'd like to have the ability to configure a connection name through an environment variable.
This way we can easily identify the connections with e.g. the K8S pod name.
Currently, it is configured so that it is AMQProxy + version https://github.com/cloudamqp/amqproxy/blob/main/src/amqproxy/upstream.cr#L235 and is thus displayed as 👇, which does not help us a lot to identify where the actual connection is coming from, without having to match IP addresses
The text was updated successfully, but these errors were encountered:
Kubernetes exposes the podname via the `gethostname` glibc call. This
will show the podname as the easy to read identifier for the connection.
Fixes#187
Could expose it as a config variable too, but I think this addresses the
need and is much simplier, both as a patch and for the user to use.
👋
We'd like to have the ability to configure a connection name through an environment variable.
This way we can easily identify the connections with e.g. the K8S pod name.

Currently, it is configured so that it is AMQProxy + version https://github.com/cloudamqp/amqproxy/blob/main/src/amqproxy/upstream.cr#L235 and is thus displayed as 👇, which does not help us a lot to identify where the actual connection is coming from, without having to match IP addresses
The text was updated successfully, but these errors were encountered: