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 eb583ab
Browse filesBrowse the repository at this point in the historyBrowse files
feat(webapp): turn on progressive trace loading and trace API paging for everyone
The run page now loads large traces progressively and updates live runs
incrementally, and the run trace API can page large traces with
`page[size]` and `page[after]`.
Mono-RevId: 928f7102a88b948176d94a9da1f0420866aa5193
The run page now loads large traces progressively and updates live runs incrementally, so big traces open faster and open run pages no longer reload the whole trace while a run is executing. The run trace API can also page large traces.
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`.
9
7
10
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.
@@ -13,8 +11,6 @@ For a finished run, spans that finish more than 7 days after the run are returne
13
11
14
12
## Page large traces
15
13
16
-
<RollingOutflag="publicTracePagingEnabled" />
17
-
18
14
The tree response stops at a size limit. To get every span of a large trace, page it: send `page[size]` (1,000–10,000) on the first request, then pass each response's `pagination.next` back as `page[after]` until it's absent.
0 commit comments