openstack/osprofiler
Code Issues Proposed changes
OpenStack cross service/project profiler
500 Commits 2 Branches 82 Tags 4.8 MiB
Python 93.4%
HTML 4.7%
Shell 1.9%
master
Go to file
Zuul 995f477632 Merge "Drop remaining pin of elasticsearch"
2024-11-19 09:35:26 +00:00
devstack add support of otlp exporter 2023-05-10 10:18:48 +02:00
doc profiler: add python requests profile 2023-06-01 08:44:08 +02:00
osprofiler Merge "Replace deprecated constant_time_compare" 2024-11-19 02:30:22 +00:00
playbooks Automatic configuration of SQLAlchemy driver in DevStack 2019-05-16 12:03:00 +02:00
releasenotes Remove Python 3.8 support 2024-10-16 11:45:21 +09:00
tools Adding pre-commit 2020-10-09 11:07:15 +02:00
.gitignore Fix api index and module index 2022-02-17 22:35:09 +00: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 Remove Python 3.8 support 2024-10-16 11:45:21 +09:00
bindep.txt Add functional test for Redis driver 2017-11-29 14:57:33 +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
requirements.txt Merge "Declare Python 3.10 support" 2023-11-16 17:50:33 +00:00
setup.cfg Remove Python 3.8 support 2024-10-16 11:45:21 +09:00
setup.py [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 11:24:14 +01:00
test-requirements.txt Drop remaining pin of elasticsearch 2024-11-19 11:54:00 +09:00
tox.ini tox: Add functional-py38, functional-py39 envs 2023-02-06 14:13:57 +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).