Open Stack

Does the proxy-logging code use the eventlet.wsgi posthook for the logging?
>From a quick inspection of the code, it seems to add a generator to the
filter layers passing the object along. Could we avoid that by using the
posthook? Or was there some other reason for not using the posthook?


On Thu, Jan 10, 2013 at 1:24 PM, Leandro Reox <leandro.reox at gmail.com>wrote:

> Yep, im planning to debug the current middleware to see if i can submit a
> fix or find my real problem and if it gets to dirty go to custom logging
> code
>
> Thanks pete
>
> Any other experiences will be very appreciated :)
>
>
> On Thu, Jan 10, 2013 at 2:59 PM, Pete Zaitcev <zaitcev at redhat.com> wrote:
>
>> On Thu, 10 Jan 2013 12:37:57 -0300
>> Leandro Reox <leandro.reox at gmail.com> wrote:
>>
>> > When we turn off the proxy-logging middleware, everything starts to
>> > response like a charm 8ms or so vs 800-1400ms !!!
>>
>> At a guess, maybe the proxy-logging middle accidentially tries
>> to resolve an IP address somewhere?
>>
>> > And i cant find the way to log locally on debug mode without activating
>> the
>> > proxy-logging middleware
>>
>> Indeed, in the past I had to resort to custom logging code
>> in instances like that.
>>
>> -- Pete
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130110/0a359f05/attachment.html>