RabbitMQ monitoring app shows load balancer IP instead of client IP

[runabol]

When behind a load balancer, the RabbitMQ admin console shows the IP address of the load balancer for each connection -- instead of the original client IP. Would be great if there was a way to pass it along somehow when creating the connection.

[michaelklishin]

@creactiviti as far as RabbitMQ is concerned, the connection to it is indeed from the load balancer. There is no way for it to know how many proxies are involved. The same is true for client libraries.

[squaremo]

That's true, @michaelklishin, but perhaps the ability to put the origin IP in a client property would help, for debugging purposes at least. Is that your motivation, @creactiviti?

[runabol]

That's exactly right @squaremo -- thank you for clarifying that. Being able to provide an arbitrary suffix (in my case it would be the client's host ip) to the client property, visible on the console would totally work.

[squaremo]

OK, the code in master will let you supply additional clientProperties when you connect. It looks like this:

var amqp = require('amqplib');
amqp.connect('amqp://localhost', {clientProperties: {'IP': '10.0.0.3'}}).then(...);

The client property is visible in the management console if you go look at that specific connection; and, it'll be output by e.g., rabbitmqctl list_connections client_properties.

[runabol]

This is perfect. Thank you very much @squaremo. Any ETA on when it will be available on npmjs ?

[squaremo]

I'll have a look at the backlog and see if there's anything else I want to include -- otherwise, it can be a v0.2.2 pretty soon.