OpenStack cross service/project profiler
55b0542eaa
The placement service has a separate config file that also needs to be modified if osprofiler is enabled in devstack. Change-Id: I7fa963b20498549d4241ccb16cfbca8ddf70eef5 |
||
---|---|---|
devstack | ||
doc | ||
osprofiler | ||
playbooks | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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://opendev.org/openstack/osprofiler
- Bugs: https://bugs.launchpad.net/osprofiler
- Release notes: https://docs.openstack.org/releasenotes/osprofiler