yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #01559
[Bug 975589] Re: Improve API logging
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => grizzly-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/975589
Title:
Improve API logging
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Nova's API logging (in nova.api.openstack.wsgi) has a few problems:
1) It mixes in error information with what's traditionally thought of
as "access" logging, making it hard to parse. It also puts a lot of
english into the responses (e.g., "returned with HTTP 200").
2) Requests are double-logged, once with the request method, once with
the status code.
3) Complete information isn't always logged. E.g., if any of the
various returns are hit in _process_stack, the response status isn't
logged.
4) Other useful information isn't captured.
I think we need to move the debug data to a separate log channel
(e.g., "nova.api.openstack.wsgi.error"), normalise the access log
format and capture, and add the following :
- User-Agent request header (so we can start to understand what tools are using the API)
- Request body size in bytes
- Request Content-Type
- Response body size in bytes
- Response Content-Type
- time to service request (for performance metrics)
I'm willing to do this work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/975589/+subscriptions