OpenStack cross service/project profiler
Go to file
Vieri 48a3de18f8 Update min tox version to 2.0
The commands used by constraints need at least tox 2.0.  Update to
reflect reality, which should help with local running of constraints
targets.

Change-Id: I871c0eff718af5196bb0f208686398dc42760309
2018-11-02 07:04:55 +00:00
devstack In DevStack install Redis client library via pip, not as system package 2018-10-17 13:37:26 +02:00
doc Update documentation & usage for redis driver 2018-06-01 10:32:34 +07:00
osprofiler When shortening span-ids, check if they're already short 2018-10-09 07:37:11 +03:00
releasenotes Update reno for stable/rocky 2018-07-26 12:41: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 Update .gitreview for new namespace 2015-10-17 22:34:15 +00:00
.stestr.conf Switch to stestr 2018-07-11 07:50:25 +07:00
.zuul.yaml Use templates for cover and lower-constraints 2018-09-07 15:31:22 +02: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 Add release note link in README 2018-06-28 00:37:30 +08: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 build universal wheels 2018-10-02 18:25:32 -04:00
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Switch to stestr 2018-07-11 07:50:25 +07:00
tox.ini Update min tox version to 2.0 2018-11-02 07:04:55 +00:00

README.rst

Team and repository tags

image

OSProfiler -- Library for cross-project profiling library

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