[openstack-dev] Proposed Logging Standards
sean at dague.net
Wed Jan 29 11:59:10 UTC 2014
On 01/28/2014 10:53 PM, Vishvananda Ishaya wrote:
> On Jan 27, 2014, at 6:57 PM, Christopher Yeoh <cbkyeoh at gmail.com
> <mailto:cbkyeoh at gmail.com>> wrote:
>> On Tue, Jan 28, 2014 at 12:55 AM, Sean Dague <sean at dague.net
>> <mailto:sean at dague.net>> wrote:
>> On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote:
>> > Hi Sean,
>> > 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>.
>> > 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!
>> Do we have many that aren't either DEBUG or TRACE? I thought we were
>> pretty clean there.
>> > Cheers,
>> > Matt
>> > P.S. FWIW, I'd also welcome details on what the "Audit" level
>> gives us that the others don't... :)
>> Well as far as I can tell the AUDIT level was a prior drive by
>> contribution that's not being actively maintained. Honestly, I
>> think we
>> should probably rip it out, because I don't see any in tree tooling to
>> use it, and it's horribly inconsistent.
>> For the uses I've seen of it in the nova api code INFO would be
>> perfectly fine in place of AUDIT.
> +1 AUDIT was added for a specific NASA use case because we needed a
> clean feed of important actions for security compliance and many
> upstream libraries were putting out INFO logs that we did not want
> included. Safe to rip it out IMO.
Thanks for the context Vish, very helpful in understanding why some of
this stuff is there so we can unwind it sanely.
Samsung Research America
sean at dague.net / sean.dague at samsung.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 482 bytes
Desc: OpenPGP digital signature
More information about the OpenStack-dev