)]}'
{"specs/backlog/approved/request-logs-on-failure.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0388842b2bd74d1ab824ae41e500d7efc8826fda","unresolved":false,"context_lines":[{"line_number":65,"context_line":"------------"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"The Log Working Group seeks to ensure sufficient diagnostic information is"},{"line_number":68,"context_line":"logged at INFO or higher in the event of a failure. Ultimately this is"},{"line_number":69,"context_line":"probably the best solution but it\u0027s unclear how long this effort will take to"},{"line_number":70,"context_line":"complete satisfactorily. In fact I\u0027m not sure if the LWG is still formed."},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_2cc84774","line":68,"updated":"2015-09-24 15:42:43.000000000","message":"Yeah, first failure data capture (FFDC) would be ideal at the point of failure so we can get the information we need above debug level to know the current state of the system and what happened - especially in the case of NoValidHost.  Then your ELK stack doesn\u0027t have to be indexing DEBUG level logs, just INFO and above and you can trace the request through that (like we do with logstash.o.o and gate failures).","commit_id":"f2d10c3bea5cbe36df4410cf84f77049c8de0f44"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0388842b2bd74d1ab824ae41e500d7efc8826fda","unresolved":false,"context_lines":[{"line_number":97,"context_line":"Performance Impact"},{"line_number":98,"context_line":"------------------"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"Buffering the logs will consume some additional memory."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"DEBUG logs will be produced even if they\u0027re later thrown away. Users not"},{"line_number":103,"context_line":"currently logging at DEBUG who choose to enable this feature may see a small"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_2cada788","line":100,"updated":"2015-09-24 15:42:43.000000000","message":"This seems really variable depending on the API load that\u0027s happening.  So you could be swapping one resource issue (disk) for another (memory).","commit_id":"f2d10c3bea5cbe36df4410cf84f77049c8de0f44"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"0388842b2bd74d1ab824ae41e500d7efc8826fda","unresolved":false,"context_lines":[{"line_number":140,"context_line":"Dependencies"},{"line_number":141,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":142,"context_line":""},{"line_number":143,"context_line":"* Include specific references to specs and/or blueprints in nova, or in other"},{"line_number":144,"context_line":"  projects, that this one either depends on or is related to."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"* If this requires functionality of another project that is not currently used"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9a1a9d01_0c09c395","line":143,"updated":"2015-09-24 15:42:43.000000000","message":"These are all template things.\n\nI would expect dependency in oslo.log, and actually this sounds more like a cross-project spec than just nova, so might be more appropriate in oslo-specs.","commit_id":"f2d10c3bea5cbe36df4410cf84f77049c8de0f44"}]}
