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: docs/content.zh/docs/ops/traces.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,26 +33,30 @@ Flink exposes a tracing system that allows gathering and exposing traces to exte
33
33
## Reporting traces
34
34
35
35
You can access the tracing system from any user function that extends [RichFunction]({{< ref "docs/dev/datastream/user_defined_functions" >}}#rich-functions) by calling `getRuntimeContext().getMetricGroup()`.
36
-
This method returns a `MetricGroup` object via which you can report a new single span trace.
36
+
This method returns a `MetricGroup` object via which you can report a new single trace with tree of spans.
37
37
38
38
### Reporting single Span
39
39
40
40
41
41
A `Span` represents some process that happened in Flink at certain point of time for a certain duration, that will be reported to a `TraceReporter`.
42
42
To report a `Span` you can use the `MetricGroup#addSpan(SpanBuilder)` method.
43
43
44
-
Currently, we don't support traces with multiple spans. Each `Span` is self-contained and represents things like a checkpoint or recovery.
44
+
Currently, we support traces with a single tree of spans, but all the children spans have to be reported all at once in one `MetricGroup#addSpan` call.
45
+
You can not report child or parent spans independently.
Copy file name to clipboardExpand all lines: docs/content/docs/ops/traces.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,26 +33,30 @@ Flink exposes a tracing system that allows gathering and exposing traces to exte
33
33
## Reporting traces
34
34
35
35
You can access the tracing system from any user function that extends [RichFunction]({{< ref "docs/dev/datastream/user_defined_functions" >}}#rich-functions) by calling `getRuntimeContext().getMetricGroup()`.
36
-
This method returns a `MetricGroup` object via which you can report a new single span trace.
36
+
This method returns a `MetricGroup` object via which you can report a new single trace with tree of spans.
37
37
38
38
### Reporting single Span
39
39
40
40
41
41
A `Span` represents some process that happened in Flink at certain point of time for a certain duration, that will be reported to a `TraceReporter`.
42
42
To report a `Span` you can use the `MetricGroup#addSpan(SpanBuilder)` method.
43
43
44
-
Currently, we don't support traces with multiple spans. Each `Span` is self-contained and represents things like a checkpoint or recovery.
44
+
Currently, we support traces with a single tree of spans, but all the children spans have to be reported all at once in one `MetricGroup#addSpan` call.
45
+
You can not report child or parent spans independently.
<td>Detail level for reporting checkpoint spans. Possible values:
16
+
- SPAN_PER_CHECKPOINT (default): Single span per checkpoint. Aggregated sum/max for submetrics from all tasks and subtasks per checkpoint
17
+
- SPAN_PER_CHECKPOINT_WITH_TASKS: Single span per checkpoint. Same as SPAN_PER_CHECKPOINT, plus arrays of aggregated values per task.
18
+
- CHILDREN_SPANS_PER_TASK: Same as SPAN_PER_CHECKPOINT plus children spans per each task. Each task span with aggregated sum/max submetrics from subtasks.
19
+
- CHILDREN_SPANS_PER_SUBTASK: Same as CHILDREN_SPANS_PER_TASK plus children spans per each subtask. Child spans for tasks and grand-child spans for subtasks.<br/><br/>Possible values:<ul><li>"SPAN_PER_CHECKPOINT"</li><li>"SPAN_PER_CHECKPOINT_WITH_TASKS"</li><li>"CHILDREN_SPANS_PER_TASK"</li><li>"CHILDREN_SPANS_PER_SUBTASK"</li></ul></td>
0 commit comments