[rabbitmq-discuss] Firehose behaviour for acks

Simon MacMullen simon at rabbitmq.com
Thu Aug 8 10:09:45 BST 2013

Yes, that's a limitation.

There's a half worked on patch somewhere to get the firehose to 
(optionally) report on all AMQP methods. I abandoned it because it was 
quite involved and it wasn't obvious anyone would care.

In the absence of that, the only real option is to use the Java client's 
AMQP tracer proxy instead: http://www.rabbitmq.com/api-guide.html#tracer 
- or something like Wireshark.

Cheers, Simon

On 07/08/2013 7:11PM, Gotthard, Petr wrote:
> Hello,
> I’d need to know when messages get delivered to consumers, but the
> Firehose Tracer publishes the "deliver.queuename" message only when the
> message leaves the broker. Unfortunately, it’s not enough for us to know
> that the message left the broker, we really need to know it has been
> delivered.
> Did you ever come across this problem?
> One solution could be to modify the Firehose to send some tracing
> message after ack has been received. If we propose such extension, is
> there a chance to get it accepted into the mainstream? Or you have some
> other solution in mind?
> Thanks,
> Petr
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Simon MacMullen
RabbitMQ, Pivotal

More information about the rabbitmq-discuss mailing list