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
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
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
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,
