OpenStack cross service/project profiler
Go to file
shangxiaobj ea1e11b68f Update the invalid doc links to the right ones in osprofiler docs
1) Fix the invalid doc links according to the lastest OpenStack Website.
2) Replace them with the right ones.

Change-Id: I8d768802e25944a9761263cb2c80f5aaca317e96
2018-01-01 22:57:13 -08:00
devstack Make collector configurable in DevStack plugin 2017-12-15 15:07:18 +01:00
doc Update the invalid doc links to the right ones in osprofiler docs 2018-01-01 22:57:13 -08:00
osprofiler Add functional test for Redis driver 2017-11-29 14:57:33 +01:00
releasenotes Remove setting of version/release from releasenotes 2017-11-16 21:56:16 +01:00
tools Trivial: Remove vim header from source files 2016-09-24 05:25:17 +08:00
.gitignore Update .gitignore 2017-07-06 16:24:38 +05:30
.gitreview Update .gitreview for new namespace 2015-10-17 22:34:15 +00:00
.testr.conf Add functional test for notifier backend 2016-12-15 19:36:35 +05:30
.zuul.yaml Add Zuul job for functional testing 2017-11-08 08:56:17 +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
README.rst Update the invalid doc links to the right ones in osprofiler docs 2018-01-01 22:57:13 -08:00
bindep.txt Add functional test for Redis driver 2017-11-29 14:57:33 +01:00
requirements.txt Remove dependency on oslo.log library 2017-08-29 10:21:50 +02:00
setup.cfg Update URLs in documents according to document migration 2017-07-13 17:39:15 +08:00
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Switch from oslosphinx to openstackdocstheme 2017-07-06 21:38:42 +00:00
tox.ini Add Zuul job for functional testing 2017-11-08 08:56:17 +01: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).