OpenStack cross service/project profiler
Go to file
Ilya Shakhat 8c264eb0fe Reload keystone to apply osprofiler config
In DevStack Keystone is configured and started within the same phase
(while other services allow to be configured before starting). To apply
osprofiler configuration, Keystone needs to be reloaded.

Change-Id: Icf69c4e7f602702cf68986a6073b2cd4c0c3abe8
2019-01-11 12:26:17 +01:00
devstack Reload keystone to apply osprofiler config 2019-01-11 12:26:17 +01:00
doc Update documentation & usage for redis driver 2018-06-01 10:32:34 +07:00
osprofiler In case of an error, always add message 2018-12-16 15:48:15 +02: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 Change openstack-dev to openstack-discuss 2018-12-04 16:34:02 +00: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).