)]}'
{"keystone/tests/core.py":[{"author":{"_account_id":220,"name":"Haneef Ali","email":"haneef.ali@hp.com","username":"haneef"},"change_message_id":"82739acf63a24d1e306b2fac2e666ca5e0913c42","unresolved":false,"context_lines":[{"line_number":411,"context_line":"        # without having a CONF object to setup logging. This should help to"},{"line_number":412,"context_line":"        # reduce the log size by limiting what we log (similar to how Keystone"},{"line_number":413,"context_line":"        # would run under mod_wsgi or eventlet)."},{"line_number":414,"context_line":"        for pair in CONF.default_log_levels:"},{"line_number":415,"context_line":"            mod, _sep, level_name \u003d pair.partition(\u0027\u003d\u0027)"},{"line_number":416,"context_line":"            logger \u003d logging.getLogger(mod)"},{"line_number":417,"context_line":"            if sys.version_info \u003c (2, 7):"}],"source_content_type":"text/x-python","patch_set":1,"id":"baada198_643efe8c","line":414,"updated":"2014-07-11 21:13:45.000000000","message":"Can\u0027t we start using logging.conf instead of adding module level logs in keystone.conf. Then it is easy to control via test_logging.conf","commit_id":"1cddf40a4b470eecf990e8914da3ec41422a216c"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"2a1ee5c71552f76a4f5e49c379757ef021bb5c9a","unresolved":false,"context_lines":[{"line_number":411,"context_line":"        # without having a CONF object to setup logging. This should help to"},{"line_number":412,"context_line":"        # reduce the log size by limiting what we log (similar to how Keystone"},{"line_number":413,"context_line":"        # would run under mod_wsgi or eventlet)."},{"line_number":414,"context_line":"        for pair in CONF.default_log_levels:"},{"line_number":415,"context_line":"            mod, _sep, level_name \u003d pair.partition(\u0027\u003d\u0027)"},{"line_number":416,"context_line":"            logger \u003d logging.getLogger(mod)"},{"line_number":417,"context_line":"            if sys.version_info \u003c (2, 7):"}],"source_content_type":"text/x-python","patch_set":1,"id":"baada198_879b1465","line":414,"in_reply_to":"baada198_643efe8c","updated":"2014-07-11 21:54:33.000000000","message":"Logging.conf works just fine for production. There is some parsing that is done on the infra-side to handle searching logs. this means all projects should have a sane default. \n\nFor now (for testing) we will continue to use the default formats provided by oslo.","commit_id":"1cddf40a4b470eecf990e8914da3ec41422a216c"},{"author":{"_account_id":4,"name":"Dolph Mathews","email":"dolph.mathews@gmail.com","username":"dolph"},"change_message_id":"ff84cfa41165b9fde1b8221a28e477fddc0088af","unresolved":false,"context_lines":[{"line_number":411,"context_line":"        # without having a CONF object to setup logging. This should help to"},{"line_number":412,"context_line":"        # reduce the log size by limiting what we log (similar to how Keystone"},{"line_number":413,"context_line":"        # would run under mod_wsgi or eventlet)."},{"line_number":414,"context_line":"        for pair in CONF.default_log_levels:"},{"line_number":415,"context_line":"            mod, _sep, level_name \u003d pair.partition(\u0027\u003d\u0027)"},{"line_number":416,"context_line":"            logger \u003d logging.getLogger(mod)"},{"line_number":417,"context_line":"            if sys.version_info \u003c (2, 7):"}],"source_content_type":"text/x-python","patch_set":1,"id":"baada198_076624bb","line":414,"in_reply_to":"baada198_643efe8c","updated":"2014-07-11 21:50:51.000000000","message":"that\u0027s how i used to do it myself - i don\u0027t even know if it still works :-/","commit_id":"1cddf40a4b470eecf990e8914da3ec41422a216c"}]}