OpenStack cross service/project profiler
Go to file
yangkun.lc 0953c65eff Start README.rst with a better title
Change-Id: I1b18c752dcc2d11144c1b92d9161faef4ad71956
2020-03-11 14:57:08 +00:00
devstack Support standalone placement in the devstack 2019-06-13 15:27:36 +02:00
doc Replace git.openstack.org URLs with opendev.org URLs 2019-04-29 06:48:18 +00:00
osprofiler Merge "Handle driver initialization errors to avoid service crash" 2019-11-18 17:24:16 +00:00
playbooks Automatic configuration of SQLAlchemy driver in DevStack 2019-05-16 12:03:00 +02:00
releasenotes Update master for stable/train 2019-09-20 16:42:30 +00:00
tools Trivial: Remove vim header from source files 2016-09-24 05:25:17 +08:00
.gitignore Switch to stestr 2018-07-11 07:50:25 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:44:00 +00:00
.stestr.conf Allow test path to be overridden 2019-01-08 16:07:27 +01:00
.zuul.yaml Switch to Ussuri jobs 2019-10-25 14:58:41 +08: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
README.rst Start README.rst with a better title 2020-03-11 14:57:08 +00:00
bindep.txt Add functional test for Redis driver 2017-11-29 14:57:33 +01:00
lower-constraints.txt Switch to stestr 2018-07-11 07:50:25 +07:00
requirements.txt Add minimum version and fix dulwich issue 2018-06-25 19:00:16 +07:00
setup.cfg Add Python 3 Train unit tests 2019-07-05 15:12:53 -04:00
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Fix elasticsearch version in python requirements 2019-04-28 15:05:38 -06:00
tox.ini Add Python 3 Train unit tests 2019-07-05 15:12:53 -04:00

README.rst

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