Just a follow-up in case you didn't see it: Abishek has started a thread [1] on the openstack-dev mailing list to discuss this. Feel free to contribute there. BR, Simon [1] http://lists.openstack.org/pipermail/openstack-dev/2015-May/064842.html On Wed, May 20, 2015 at 2:39 PM, Simon Pasquier <spasquier at mirantis.com> wrote: > Hi, > During the ops session on logging [0], we discussed how to correlate > between request ids when a request crosses service boundaries. > I'd encourage everybody interested by this effort to look at the proposed > specifications [1] [2] and provide feedback. One of the questions raised is > whether it makes sense to have a unique request id or different request ids > per service with a way to map them together. > BR, > Simon > > [0] https://etherpad.openstack.org/p/YVR-ops-logging > [1] https://review.openstack.org/#/c/156508/ > [2] https://review.openstack.org/#/c/164582/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150527/083cc028/attachment.html>