OpenStack cross service/project profiler
Go to file
Ilya Shakhat 17f8441e28 Make test_notifier independent of test case execution order
Test_notifier contains a test case that verifies default notifier value
(test_get_default_notifier) and there are 2 test cases that update
default notifier value. It's supposed that test_get_default_notifier
is executed first, otherwise it gets wrong value. Test's tearDown()
method was designed to restore default notifier, but failed to do so
due to wrong reference to global variable.

Change-Id: Id083f1e8ba4bf2a0341eb1a7ee8891b53c1f3a65
2017-08-10 14:21:02 +02:00
devstack Expose connection_string parameter into DevStack plugin 2017-06-14 14:58:47 +02:00
doc doc: Fix formatting 2017-07-06 21:50:47 +00:00
osprofiler Make test_notifier independent of test case execution order 2017-08-10 14:21:02 +02:00
releasenotes Update reno for stable/pike 2017-07-28 21:06:02 +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
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 Update URLs in documents according to document migration 2017-07-13 17:39:15 +08:00
requirements.txt Merge "Replace logging with oslo_log" 2016-11-11 17:30:09 +00: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 Switch from oslosphinx to openstackdocstheme 2017-07-06 21:38:42 +00:00
tox.ini Python 3.4 support is removed 2017-03-08 12:37:37 +05:30

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