cdb6e83ed1
Messaging driver is extended to read profiling events from RabbitMQ and generate report. This simplifies usage of profiling in DevStack since Ceilometer is not needed anymore. The typical workflow is following: 1. User issues a command with profiling enabled: openstack --os-profile SECRET KEY <command> 2. User retrieves the trace: osprofiler trace show --connection messaging:// --transport-url rabbit://<rabbituser>:<rabbitpassword>@<devstack>:5672/ --json <trace-id> Change-Id: I950896d6d9156f09e378bdfcf272aef5da4ece74 |
||
---|---|---|
devstack | ||
doc | ||
osprofiler | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
OSProfiler -- Library for cross-project profiling library
OSProfiler provides a tiny but powerful library that is used by most (soon to be all) OpenStack projects and their python clients. It provides functionality to be able to generate 1 trace per request, that goes through all involved services. This trace can then be extracted and used to build a tree of calls which can be quite handy for a variety of reasons (for example in isolating cross-project performance issues).
- Free software: Apache license
- Documentation: https://docs.openstack.org/osprofiler/latest/
- Source: https://git.openstack.org/cgit/openstack/osprofiler
- Bugs: https://bugs.launchpad.net/osprofiler