Open Stack

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" <boris at 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_xzdong at 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-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160307/8efb5d8c/attachment.html>