OpenStack cross service/project profiler
Go to file
Hervé Beraud e29b187151 Fix formattiing of release list
Change-Id: Ib8ac1b8288889789814334b384149ed19c8b4ef1
2022-05-27 14:04:22 +02:00
devstack Set manila config opts in devstack 2021-08-02 17:16:25 +00:00
doc Make some revisions in the document 2022-03-31 12:00:53 +08:00
osprofiler Fix api index and module index 2022-02-17 22:35:09 +00:00
playbooks Automatic configuration of SQLAlchemy driver in DevStack 2019-05-16 12:03:00 +02:00
releasenotes Fix formattiing of release list 2022-05-27 14:04:22 +02:00
tools Adding pre-commit 2020-10-09 11:07:15 +02:00
.gitignore Fix api index and module index 2022-02-17 22:35:09 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:44:00 +00:00
.pre-commit-config.yaml Move flake8 as a pre-commit local target. 2021-03-23 13:17:30 +01:00
.stestr.conf Allow test path to be overridden 2019-01-08 16:07:27 +01:00
.zuul.yaml Update CI to use unversioned jobs template 2022-03-15 15:07:56 +00:00
bindep.txt Add functional test for Redis driver 2017-11-29 14:57:33 +01:00
CONTRIBUTING.rst Update the invalid doc links to the right ones in osprofiler docs 2018-01-01 22:57:13 -08:00
LICENSE Init Strucutre of lib 2014-01-09 11:25:23 +04:00
lower-constraints.txt Fix api index and module index 2022-02-17 22:35:09 +00:00
README.rst Start README.rst with a better title 2020-03-11 14:57:08 +00:00
requirements.txt Merge "Remove six" 2021-10-04 18:32:28 +00:00
setup.cfg Add py38 package metadata 2020-04-24 08:23:14 -05:00
setup.py [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 11:24:14 +01:00
test-requirements.txt Fix api index and module index 2022-02-17 22:35:09 +00:00
tox.ini Fix api index and module index 2022-02-17 22:35:09 +00:00

OSProfiler -- Library for cross-project profiling

image

Latest Version

Downloads

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).