Good news, thanks. The next question would be is it possible to selectively trace publish OR deliver, rather than both simultaneously?<br><br><div class="gmail_quote">On Mon, Apr 2, 2012 at 2:18 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 31/03/12 13:27, Brendan Hay wrote:<br>
</div><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The firehose tracer would be ideal for this, but it has a big fat<br>
disclaimer about performance implications.<br>
</blockquote>
<br></div>
I should probably change that - the performance implications are not bad per se, it's just that you may end up publishing firehose messages for every publish / deliver (i.e. pretty much as you would expect).<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br>