[openstack-dev] [mistral][freezer] adopting oslo.context for logging debugging and tracing

Renat Akhmerov renat.akhmerov at gmail.com
Fri May 26 04:45:54 UTC 2017

Thanks Doug. We’ll look into this.

@Tuan, is there any roadblocks with the patch you’re working on? [1]

[1] https://review.openstack.org/#/c/455407/


On 26 May 2017, 01:54 +0700, Doug Hellmann <doug at doughellmann.com>, wrote:
> The new work to add the exception information and request ID tracing
> depends on using both oslo.context and oslo.log to have all of the
> relevant pieces of information available as log messages are emitted.
> In the course of reviewing the "done" status for those initiatives,
> I noticed that although mistral and freezer are using oslo.log,
> neither uses oslo.context. That means neither project will get the
> extra debugging information, and neither project will see the global
> request ID in logs.
> I started looking at updating mistral's context to use oslo.context
> as a base class, but ran into some issues because of some extensions
> made to the existing class. I wasn't able to find where freezer is
> doing anything at all with an API request context.
> I'm available to help, if someone else wants to pick up the work.
> Doug
> __________________________________________________________________________
> 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/20170526/d1be07ec/attachment.html>

More information about the OpenStack-dev mailing list