openstack
/
osprofiler
Code Issues Proposed changes
OpenStack cross service/project profiler
214 Commits 2 Branches 81 Tags 4.7 MiB
Python 93.4%
HTML 4.7%
Shell 1.9%
Go to file
ChangBo Guo(gcb) 9407108fee Add reno for release notes management 
The release management team have indicated this is their preferred way
to collect release notes in future.

Closes-Bug: #1634356

Change-Id: I40ebe47509ba5cabd57ed8c4987ae6ec1e2b5d5f
 		2016-11-03 18:38:01 +08:00
devstack Merge "Enable devstack to configure OSProfiler for Senlin project" 2016-10-20 14:34:44 +00:00
doc Update the driver path in th doc 2016-10-11 10:25:18 +08:00
osprofiler Use an env variable for connection string default 2016-10-10 15:21:28 +05:30
releasenotes Add reno for release notes management 2016-11-03 18:38:01 +08:00
tools Trivial: Remove vim header from source files 2016-09-24 05:25:17 +08:00
.gitignore Add reno for release notes management 2016-11-03 18:38:01 +08:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:34:15 +00:00
.testr.conf Move osprofiler tests into osprofiler 2016-01-25 12:12:45 -08:00
CONTRIBUTING.rst Add CONTRIBUTING.rst 2016-02-29 13:42:14 +08:00
LICENSE Init Strucutre of lib 2014-01-09 11:25:23 +04:00
README.rst Continue work on standardizing osprofiler docs 2016-03-24 21:35:30 -07:00
requirements.txt Update dependencies' version from project requirements 2016-10-20 14:21:55 +00:00
setup.cfg Update homepage with developer documentation page 2016-09-24 14:37:51 +08:00
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt Add reno for release notes management 2016-11-03 18:38:01 +08:00
tox.ini Add reno for release notes management 2016-11-03 18:38:01 +08:00

README.rst

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