Hi, 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.
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. -K On Sun, Mar 6, 2016 at 11:55 PM Xuanzhou Perry Dong <oss_xzd...@163.com> wrote: > Hi, Boris, > > Thanks for your response. > > 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. > > > Best Regards, > Xuanzhou Perry Dong > > At 2016-03-07 12:27:12, "Boris Pavlovic" <bo...@pavlovic.me> wrote: > > Xuanzhou, > > 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: > https://github.com/openstack/osprofiler > > Best regards, > Boris Pavlovic > > On Sun, Mar 6, 2016 at 8:15 PM, Xuanzhou Perry Dong <oss_xzd...@163.com> > wrote: > >> Hi, >> >> 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, >> http://docs.openstack.org/liberty/config-reference/content/networking-configuring-rpc.html). >> But it seems that this oslo_messaging_amqp.trace is only available to the >> Proton driver. >> >> 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. >> >> Any response is appreciated. >> Thanks. >> Best Regards, >> Xuanzhou Perry Dong >> >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev