openstack
/
osprofiler
Code Issues Proposed changes
OpenStack cross service/project profiler
348 Commits 2 Branches 81 Tags 4.7 MiB
Python 93.4%
HTML 4.7%
Shell 1.9%
Go to file
Tovin Seven 113a2ddddd Filter traces that contain error/exception 
Adds ability to filter error traces to OSProfiler.
Adds command for list error traces.

Change-Id: I0ec97337cae5e573fedae2b6665aa73a73fe3654
 		2018-02-05 15:14:17 +07:00
devstack Remove Ceilometer support 2018-01-18 12:01:09 +01:00
doc Remove Ceilometer support 2018-01-18 12:01:09 +01:00
osprofiler Filter traces that contain error/exception 2018-02-05 15:14:17 +07: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 Zuul: Remove project name 2018-02-01 22:25:06 -08: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 Add initial 'trace list' command 2018-01-23 13:31:04 +01: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 Remove Ceilometer support 2018-01-18 12:01:09 +01: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).