OpenStack cross service/project profiler
Go to file
Wander Way 951efdce13 Uncap PrettyTable
This is now maintained as a Jazzband project [1].

[1] https://github.com/jazzband/prettytable

Change-Id: I8b1d3e2d5354b89577ca13eda1acb704c9429fbf
2021-05-17 09:14:46 +00:00
devstack Support standalone placement in the devstack 2019-06-13 15:27:36 +02:00
doc Adding pre-commit 2020-10-09 11:07:15 +02:00
osprofiler Adding pre-commit 2020-10-09 11:07:15 +02:00
playbooks Automatic configuration of SQLAlchemy driver in DevStack 2019-05-16 12:03:00 +02:00
releasenotes Update master for stable/victoria 2020-09-11 21:03:12 +00:00
tools Adding pre-commit 2020-10-09 11:07:15 +02:00
.gitignore ignore reno generated artifacts 2020-09-22 11:08:09 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:44:00 +00:00
.pre-commit-config.yaml Move flake8 as a pre-commit local target. 2021-03-23 13:17:30 +01:00
.stestr.conf Allow test path to be overridden 2019-01-08 16:07:27 +01:00
.zuul.yaml Dropping lower constraints testing 2020-12-18 15:15:05 +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
README.rst Start README.rst with a better title 2020-03-11 14:57:08 +00:00
bindep.txt Add functional test for Redis driver 2017-11-29 14:57:33 +01:00
lower-constraints.txt switch to importlib.metadata to find package version 2020-07-06 11:07:17 +02:00
requirements.txt Uncap PrettyTable 2021-05-17 09:14:46 +00:00
setup.cfg Add py38 package metadata 2020-04-24 08:23:14 -05:00
setup.py [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 11:24:14 +01:00
test-requirements.txt Adding pre-commit 2020-10-09 11:07:15 +02:00
tox.ini Use py3 as the default runtime for tox 2020-11-04 10:06:29 +01:00

README.rst

OSProfiler -- Library for cross-project profiling

image

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