[openstack-dev] Proposed Logging Standards
Sanchez, Cristian A
cristian.a.sanchez at intel.com
Wed Jan 29 17:57:02 UTC 2014
I¹m interested to help in this switch to python logging framework for
shipping to logstash/etc. Are you working on a blueprint for this?
On 27/01/14 11:07, "Macdonald-Wallace, Matthew"
<matthew.macdonald-wallace at hp.com> wrote:
>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"
>P.S. FWIW, I'd also welcome details on what the "Audit" level gives us
>that the others don't... :)
>> -----Original Message-----
>> From: Sean Dague [mailto:sean at dague.net]
>> Sent: 27 January 2014 13:08
>> To: OpenStack Development Mailing List
>> Subject: [openstack-dev] Proposed Logging Standards
>> Back at the beginning of the cycle, I pushed for the idea of doing some
>> harmonization, so that the OpenStack logs, across services, made sense.
>> pushed a proposed changes to Nova and Keystone over the past couple of
>> This is going to be a long process, so right now I want to just focus
>> INFO level sane, because as someone that spends a lot of time staring
>>at logs in
>> test failures, I can tell you it currently isn't.
>> https://wiki.openstack.org/wiki/LoggingStandards is a few things I've
>> down so far, comments welcomed.
>> We kind of need to solve this set of recommendations once and for all
>> because negotiating each change, with each project, isn't going to work
>> What I'd like to find out now:
>> 1) who's interested in this topic?
>> 2) who's interested in helping flesh out the guidelines for various log
>> 3) who's interested in helping get these kinds of patches into various
>> 4) which projects are interested in participating (i.e. interested in
>> landing these kinds of UX improvements)
>> This is going to be progressive and iterative. And will require lots of
>> Sean Dague
>> Samsung Research America
>> sean at dague.net / sean.dague at samsung.com
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev