Jump to: navigation, search

Oslo/blueprints/logging-and-notification

< Oslo
Revision as of 09:47, 18 October 2013 by JulienDanjou (talk | contribs) (Created page with "= Context = Currently all OpenStack projects use the ''openstack.common.log' module to log messages of various level, info, debug, warn, etc. The ''openstack.common.log'' mod...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Context

Currently all OpenStack projects use the openstack.common.log' module to log messages of various level, info, debug, warn, etc. The openstack.common.log module relies on the standard Python logging module to format and record log.

Problem

There's a lot of analytics that could be done if we were able to receive applications logs in real time. However this is for now impossible.

The only way to receive information from the applications is to make them use the openstack.common.notifier module, which requires a lot of head code change upfront. Today, everything that's logged is logged into a standard destination such as syslog or a file.

Proposed solution

The proposed solution is to provide a logging driver that would be the openstack.common.notifier module. Operators could configure the standard Python logging module as usual and be able to send certain log to a file and/or also to the notification system. These logs could be sent as notifications and then consumed by others programs such as Ceilometer.