diff options
author | zhaolei.lc <15247232416@163.com> | 2022-03-31 10:45:12 +0800 |
---|---|---|
committer | zhaolei.lc <15247232416@163.com> | 2022-03-31 12:00:53 +0800 |
commit | 32863011fe90aa283425b6347123c38e5c251ac3 (patch) | |
tree | c0ee42a0f9b95fb991ec58e07ad15992cad95ecf /doc/source/user/api.rst | |
parent | 4bc4ed011750927306c0f1706843eac071cc5dc2 (diff) | |
download | osprofiler-32863011fe90aa283425b6347123c38e5c251ac3.tar.gz |
Make some revisions in the document3.4.3
Make some revisions about the example of the
implementation of nested trace points and fix
some typos.
Change-Id: I26a791e1073a2d62bd0f1c79bc26cd898d4e2c55
Diffstat (limited to 'doc/source/user/api.rst')
-rw-r--r-- | doc/source/user/api.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/source/user/api.rst b/doc/source/user/api.rst index 03111e2..a29b181 100644 --- a/doc/source/user/api.rst +++ b/doc/source/user/api.rst @@ -76,14 +76,14 @@ How profiler works? .. code-block:: python profiler.start("parent_point") # trace_stack.push(<new_uuid>) - # send to collector -> trace_stack[-2:] + # send to collector -> trace_stack[1] - profiler.start("parent_point") # trace_stack.push(<new_uuid>) - # send to collector -> trace_stack[-2:] - profiler.stop() # send to collector -> trace_stack[-2:] + profiler.start("child_point") # trace_stack.push(<new_uuid>) + # send to collector -> trace_stack[2] + profiler.stop() # send to collector -> trace_stack[2] # trace_stack.pop() - profiler.stop() # send to collector -> trace_stack[-2:] + profiler.stop() # send to collector -> trace_stack[1] # trace_stack.pop() It's simple to build a tree of nested trace points, having |