OpenStack consists of multiple projects. Each project, in turn, is composed of multiple services. To process some request, e.g. to boot a virtual machine, OpenStack uses multiple services from different projects. In the case something works too slowly, it's extremely complicated to understand what exactly goes wrong and to locate the bottleneck.
To resolve this issue, we introduce a tiny but powerful library, osprofiler, that is going to be used by all OpenStack projects and their python clients. To be able to generate 1 trace per request, that goes through all involved services, and builds a tree of calls (see an example http://
For more details take a look at:
https:/
View full history Series and milestones
trunk series is the current focus of development.
All bugs Latest bugs reported
-
Bug #2008170: jaeger driver can not send spans to agent
Reported -
Bug #2006611: jaeger - add tags to use as process-wide tracer tags
Reported -
Bug #2003092: jaeger - add service name prefix
Reported -
Bug #1922816: allow enable/disable osprofiler in the flight
Reported -
Bug #1827480: osprofiler fails when it is configed with mongon
Reported
All blueprints Latest blueprints
-
Filter error traces in OSprofiler to separated place
Registered -
Tail-based coherent sampling [1] in OSProfiler
Registered -
Asynchronous trace collection in OSProfiler
Registered -
Make OSProfiler compatible with OpenTracing API
Registered -
Overhead control in OSProfiler
Registered
More contributors Top contributors
- Sahid Orentino 11 points
- ahongloumeng 3 points