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
{{ message }}
Repository navigation
Commit de97106
Browse filesBrowse the repository at this point in the historyBrowse files
fix(webapp): bound trace API ClickHouse reads by run completion
Bound the time window the run trace API reads for finished runs, so
retrieving
the trace of an old run no longer scans every day of stored events since
the
run was created.
For a finished run, events stored more than 7 days after the run
completed are
no longer read. In rare cases, a span that finishes more than 7 days
after the
run, or a cancellation the run would inherit from a parent recorded that
late,
is not reflected: the span is returned in its last recorded state. Runs
that
are still executing are not affected.
Mono-RevId: 549b041b446c38ab61e8ce68c809a8d376df3dd6
Copy file name to clipboardExpand all lines: docs/management/runs/retrieve-trace.mdx
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,3 +6,5 @@ openapi: "v3-openapi GET /api/v1/runs/{runId}/trace"
6
6
Returns the OpenTelemetry trace subtree for the run you request. The response `trace.rootSpan` is that run's span — not necessarily the trace-wide root — with its descendant spans nested under `children`.
7
7
8
8
For a child or nested run inside a large trace, this endpoint scopes the tree to that run so you still get a useful subtree even when the full trace has more spans than the platform can return in one response.
9
+
10
+
For a finished run, spans that finish more than 7 days after the run are returned in their last recorded state.
0 commit comments