[spike] RabbitMQ: Investigate setting "consumer tag" via Bunny or Sneakers #5440
Description
This will make it easier to see what apps are connected to RabbitMQ, since right now (in the RabbitMQ dashboard) all we see is the load balancer IP that they go through, so it's hard to differentiate the actual incoming connections.
It's rare, but sometimes apps get disconnected from RabbitMQ after network outages, VM restarts, and other unusual blips. Right now, when we are suspicious that's the case, we just redeploy everything, since that will recreate Rabbit connections. But it'd be nice to have more insight from the Rabbit dashboard.
Basic info links, though afaik, no one in the dept has experimented with this yet:
https://www.rabbitmq.com/docs/consumers#consumer-tags
http://rubybunny.info/articles/queues.html
This could be useful for any message consumer that connects to Rabbit. DSA would be a good test bed, but H3, pre-assembly, and any other RabbitMQ consuming apps would benefit from this.
Can this or something similar also be used for message producers (e.g. pres cat, or anything that asks for indexing)? Is that what "delivery tags" are for?