<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type></HEAD>
<BODY>
<DIV>
<DIV style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">I think it is also good for general i18n effort </DIV></DIV>
<DIV dir=ltr>
<HR>
<SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">发件人: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href="mailto:cbkyeoh@gmail.com">Christopher Yeoh</A></SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">发送时间: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">2014/1/28 11:02</SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">收件人: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href="mailto:openstack-dev@lists.openstack.org">OpenStack Development Mailing List (not for usage questions)</A></SPAN><BR><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">主题: </SPAN><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">Re: [openstack-dev] Proposed Logging Standards</SPAN><BR><BR></DIV>
<DIV dir=ltr>
<DIV class=gmail_extra>
<DIV class=gmail_quote>On Tue, Jan 28, 2014 at 12:55 AM, Sean Dague <SPAN dir=ltr><<A href="mailto:sean@dague.net" target=_blank>sean@dague.net</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV class=im>On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote:<BR>> Hi Sean,<BR>><BR>> I'm currently working on moving away from the "built-in" logging to use log_config=<filename> and the python logging framework so that we can start shipping to logstash/sentry/<insert other useful tool here>.<BR>><BR>> I'd be very interested in getting involved in this, especially from a "why do we have log messages that are split across multiple lines" perspective!<BR><BR></DIV>Do we have many that aren't either DEBUG or TRACE? I thought we were<BR>pretty clean there.<BR>
<DIV class=im><BR>> Cheers,<BR>><BR>> Matt<BR>><BR>> P.S. FWIW, I'd also welcome details on what the "Audit" level gives us that the others don't... :)<BR><BR></DIV>Well as far as I can tell the AUDIT level was a prior drive by<BR>contribution that's not being actively maintained. Honestly, I think we<BR>should probably rip it out, because I don't see any in tree tooling to<BR>use it, and it's horribly inconsistent.<BR>
<DIV class=HOEnZb>
<DIV class=h5><BR></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>For the uses I've seen of it in the nova api code INFO would be perfectly fine in place of AUDIT.<BR><BR></DIV>
<DIV>I'd be happy to help out with patches to cleanup the logging in n-api.<BR><BR></DIV>
<DIV>One other thing to look at - I've noticed with logs is that when something like glanceclient code (just as an example) is called from nova,<BR></DIV>
<DIV>we can get ERROR level messages for say image not found when its actually perfectly expected that this will occur.<BR>I'm not sure if we should be changing the error level in glanceclient or just forcing any error logging in glanceclient when<BR>called from Nova to a lower level though.<BR></DIV>
<DIV><BR></DIV>
<DIV>Chris<BR></DIV></DIV></DIV></DIV></BODY></HTML>