openstack/osprofiler
Code Issues Proposed changes
OpenStack cross service/project profiler
366 Commits 2 Branches 82 Tags 4.8 MiB
Python 93.4%
HTML 4.7%
Shell 1.9%
6d68170f72
Go to file
Zuul 6d68170f72 Merge "Make profiler.clean() public method"
2018-07-09 16:39:57 +00:00
devstack Update documentation & usage for redis driver 2018-06-01 10:32:34 +07:00
doc Update documentation & usage for redis driver 2018-06-01 10:32:34 +07:00
osprofiler Make profiler.clean() public method 2018-06-27 12:26:55 +01:00
releasenotes Update reno for stable/queens 2018-01-24 18:09:49 +00: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 lower-constraints job 2018-04-19 09:21:21 +07: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 Add minimum version and fix dulwich issue 2018-06-25 19:00:16 +07:00
README.rst Add release note link in README 2018-06-28 00:37:30 +08:00
requirements.txt Add minimum version and fix dulwich issue 2018-06-25 19:00:16 +07:00
setup.cfg Add lower-constraints job 2018-04-19 09:21:21 +07:00
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Add minimum version and fix dulwich issue 2018-06-25 19:00:16 +07:00
tox.ini Add minimum version and fix dulwich issue 2018-06-25 19:00:16 +07: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).