You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/user_guides/portal_guides.rst
+41-1
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,11 @@ in either your :doc:`Platform Configuration File<platform>` or your
35
35
Tracing
36
36
-------
37
37
38
-
IPS (version >= 0.6.0) has the ability to capture a trace of the
38
+
.. note::
39
+
40
+
New in IPS-Framework 0.6.0
41
+
42
+
IPS has the ability to capture a trace of the
39
43
workflow to allow analysis and visualizations. The traces are captured
40
44
in the `Zipkin Span format <https://zipkin.io/zipkin-api/>`_ and
41
45
viewed within IPS portal using `Jaeger
@@ -60,3 +64,39 @@ The statistics can be further broken down by operation.
60
64
.. note::
61
65
62
66
Self time (ST) is the total time spent in a span when it was not waiting on children. For example, a 10ms span with two 4ms non-overlapping children would have self-time = 10ms - 2 * 4ms = 2ms.
67
+
68
+
69
+
Child Runs
70
+
----------
71
+
72
+
.. note::
73
+
74
+
New in IPS-Framework 0.7.0
75
+
76
+
If you have a workflow where you are running ``ips`` as a task of
77
+
another IPS simulation you can create a relation between them that
78
+
will allow it to be viewed together in the IPS-portal and get a single
79
+
trace for the entire collection.
80
+
81
+
To setup the hierarchical structure between different IPS runs, so if
82
+
one run starts other runs as a separate simulation, you can set the
83
+
``PARENT_PORTAL_RUNID`` parameter in the child simulation
84
+
configuration. This can be done dynamically from the parent simulation
0 commit comments