Description of problem: When troubleshooting production systems it is desirable to be able to trace all data base queries, web REST calls, messaging service RPC calls, libvirt API calls associated with invocation of a user command or background job. It should be able to collect timing information and stack call paths for each item and provide tools for analysing a series of requests to identify slow points / scalability issues. This bug is track the integration of a system to allow such tracing into OpenStack services.
Sort of related ... but primarily just around tracking messages between services IIRC http://www.sandywalsh.com/2012/10/debugging-openstack-with-stacktach-and.html
@danpb: I reviewed your mockup modified my generators, etc such that they no longer use RPC and the nova api, and instead just dump to stderr on SIGUSR1 (similarly to how you did it). The version object is passed as a parameter, so we don't have to actually import parts of nova from the library itself. I've placed it in 'oslo.report' (so in the patch below, copy the oslo folder into your own python packages oslo directory (installed by oslo.config). Hypothetically, it could be used in any of the other projects (with the slight modification to make sure they implement something akin to nova's version.py). How's that look?
whoops, wrong bug (similar titles)
Duplicate of RFE bug 978491 ?
(In reply to Alan Pevec from comment #5) > Duplicate of RFE bug 978491 ? No, this is not related. I'll have to write up a blueprint for this bug to clarify what I was imagining.
Attaching the current osprofiler review for openstack/nova that has missed Mitaka and is heading for Newton at the earliest.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Assigned to Lee to review and follow the progress of this specification throughout the Newton cycle.
Looks like this was not re-approved in time for Ocata.
Moving back to OSP 11, the spec and implementation actually landed in time.
Lee can you please provide some instructions for testing this? Then set NEEDINFO on panbalag for qa_ack+.
Dropping from OSP 13 as the TripleO work to wire this up during a deployment was not completed. This is now captured in 1416446 as a generic request for 14.