Hi Cristian, The functionality already exists within Openstack (certainly it's there in Nova) it's just not very well documented (something I keep meaning to do!)
Basically you need to add the following to your nova.conf file: log_config=/etc/nova/logging.conf And then create /etc/nova/logging.conf with the configuration you want to use based on the Python Logging Module's "ini" configuration format. Hope that helps, Matt > -----Original Message----- > From: Sanchez, Cristian A [mailto:cristian.a.sanc...@intel.com] > Sent: 29 January 2014 17:57 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] Proposed Logging Standards > > Hi Matthew, > 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? > Cheers, > > Cristian > > On 27/01/14 11:07, "Macdonald-Wallace, Matthew" > <matthew.macdonald-wall...@hp.com> 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! > > > >Cheers, > > > >Matt > > > >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:s...@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 log harmonization, so that the OpenStack logs, across services, > >>made sense. > >>I've > >> pushed a proposed changes to Nova and Keystone over the past couple > >>of days. > >> > >> This is going to be a long process, so right now I want to just focus > >>on making 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 > >>written down so far, comments welcomed. > >> > >> We kind of need to solve this set of recommendations once and for all > >>up front, because negotiating each change, with each project, isn't > >>going to work (e.g - > >> https://review.openstack.org/#/c/69218/) > >> > >> 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 levels? > >> 3) who's interested in helping get these kinds of patches into > >>various projects in OpenStack? > >> 4) which projects are interested in participating (i.e. interested in > >>prioritizing landing these kinds of UX improvements) > >> > >> This is going to be progressive and iterative. And will require lots > >>of folks involved. > >> > >> -Sean > >> > >> -- > >> Sean Dague > >> Samsung Research America > >> s...@dague.net / sean.da...@samsung.com http://dague.net > > > >_______________________________________________ > >OpenStack-dev mailing list > >OpenStack-dev@lists.openstack.org > >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev