openstack
/
osprofiler
Code Issues Proposed changes
OpenStack cross service/project profiler
284 Commits 2 Branches 81 Tags 4.7 MiB
Python 93.4%
HTML 4.7%
Shell 1.9%
Go to file
Vipin Balachandran 598f8ebb8d Fix error message for invalid trace 
Some of the reasons printed for invalid trace are specific
to Ceilometer. Ceilometer driver already prints authentication
failure message. Also, end-users shouldn't be concerned about
configuring Ceilometer. Updating the error message so that it
is generic enough for all backends.

Change-Id: Id44cdacaf423852458ebef6fb4e5d142ee9ee8b4
 		2017-03-22 15:41:03 +05:30
devstack Add zun to devstack config 2017-03-18 10:21:20 -05:00
doc Add Jaeger to list of similar projects 2017-03-03 14:22:42 +07:00
osprofiler Fix error message for invalid trace 2017-03-22 15:41:03 +05:30
releasenotes Update reno for stable/ocata 2017-01-20 19:16:16 +00: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 Add functional test for notifier backend 2016-12-15 19:36:35 +05:30
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 Show team and repo badges on README 2016-11-25 13:13:03 +01:00
requirements.txt Merge "Replace logging with oslo_log" 2016-11-11 17:30:09 +00:00
setup.cfg Python 3.4 support is removed 2017-03-08 12:37:37 +05:30
setup.py Use pkg_resources to get version 2016-03-10 17:54:20 +08:00
test-requirements.txt [Fix gate]Update test requirement 2017-03-02 22:13:52 +08:00
tox.ini Python 3.4 support is removed 2017-03-08 12:37:37 +05:30

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