Go to file
Ilya Shakhat d2c1bb5ffa Unify and fix list_traces function
1. Remove `filter` parameter from `list_traces` function, since
   filtering is heavily depends on a backend and cannot be (easily)
   made uniform.
2. Unify the output of `list_traces` - the function returns a list
   of `traces`, where each trace is a dictionary with at least `base_id`
   and `timestamp` fields.
3. Fix `list_traces` in Redis driver, so it returns only traces, instead
   of events.
4. Add functional test for `list_traces` in Redis driver.

Change-Id: Ia81540288fe98fd9b8e256c62cc372fa33fcbea3
2018-01-23 13:31:51 +01:00
2018-01-18 12:01:09 +01:00
2018-01-18 12:01:09 +01:00
2017-07-06 16:24:38 +05:30
2015-10-17 22:34:15 +00:00
2017-11-08 08:56:17 +01:00
2014-01-09 11:25:23 +04:00
2016-03-10 17:54:20 +08:00
2017-11-08 08:56:17 +01:00

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

Description
OpenStack cross service/project profiler
Readme 4.9 MiB
Languages
Python 93.2%
HTML 4.9%
Shell 1.9%