----- Original Message ----- > Team, > > We have a blueprint for logging architecture within Solum, which is an > important feature to aid in debugging at runtime: > > https://blueprints.launchpad.net/solum/+spec/logging > > The team voted for a lightweight governance style, and because we are > planning to skip our upcoming meeting doe to the ODS event, I plan to > approver this blueprint in the absence of any objections here on the ML, or > in #solum today. Please let me know your thoughts, as we want to be acting > on an approved blueprint before posting an implementation. > > Thanks, >
Comment I already replied to Jay in IRC about: Be sure to consider the potential impact of threading/eventlet behavior on the logging infrastructure so that attributes are bound correctly to the appropriate caller. Other than that the concept of tying user info to logging more broadly is +1 from me. _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
