<div dir="ltr"><div><div><div>Hi,<br><br></div>The 'trace' boolean offered by the AMQP 1.0 driver exposes a debug feature that is provided by the Proton library. This is specific to the Proton library - I'm not sure kombu/zmq/etc offer a similar feature.<br><br></div>As Xuanzhou points out, this debug tool merely prints to stdout a summary of each AMQP 1.0 protocol frame before it is written/after it is read from the socket. It prints the entire protocol exchange (control frames, etc) and is not limited to just the message traffic. Given that, I don't think the transport drivers can implement such a low level debug feature unless it is offered by the protocol libraries themselves.<br><br></div>-K <br><div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Mar 6, 2016 at 11:55 PM Xuanzhou Perry Dong <<a href="mailto:oss_xzdong@163.com">oss_xzdong@163.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div>Hi, Boris,<br><br>Thanks for your response.<br><br>I refer to the very simple type of "trace": just print out the RPC messages to stdout/stderr/syslog. I have checked the osprofiler project and think that it is very good and could solve my problem if it is used by the Openstack projects to trace their RPC calls.</div></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><div><br><br>Best Regards,<br>Xuanzhou Perry Dong<br></div></div><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial"><br>At 2016-03-07 12:27:12, "Boris Pavlovic" <<a href="mailto:boris@pavlovic.me" target="_blank">boris@pavlovic.me</a>> wrote:<br> <blockquote style="PADDING-LEFT:1ex;MARGIN:0px 0px 0px 0.8ex;BORDER-LEFT:#ccc 1px solid"><div dir="ltr">Xuanzhou, <br><div><br></div><div>I am not sure what do you mean by "trace". But if you need something that allows to do cross service/project tracing then you should take a look at osprofiler:</div><div><a href="https://github.com/openstack/osprofiler" target="_blank">https://github.com/openstack/osprofiler</a><br></div><div><br></div><div>Best regards,</div><div>Boris Pavlovic </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 6, 2016 at 8:15 PM, Xuanzhou Perry Dong <span dir="ltr"><<a href="mailto:oss_xzdong@163.com" target="_blank">oss_xzdong@163.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">Hi,<br><br>I am looking for a common RPC message trace mechanism in
oslo_messaging. This message trace mechanism needs to be common to all
drivers. Currently some documentation mentions that
oslo_messaging_amqp.trace can activate the message trace (say, <a href="http://docs.openstack.org/liberty/config-reference/content/networking-configuring-rpc.html%29." target="_blank">http://docs.openstack.org/liberty/config-reference/content/networking-configuring-rpc.html).</a> But it seems that this oslo_messaging_amqp.trace is only available to the Proton driver. <br><br>Do
I miss any existing common RPC message trace mechanism in oslo? If
there is no such mechanism, I would propose to create such a mechanism
for oslo.<br><br>Any response is appreciated.<br>Thanks.<br>Best Regards,<br>Xuanzhou Perry Dong<br></div><br><br><span title="neteasefooter"><p> </p></span><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br><span title="neteasefooter"><p> </p></span>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>