A tap in the page sends no span of its own #376

Closed
opened 2026-10-25 08:56:30 -07:00 by rays · 1 comment
Owner

Found reviewing what production's traces and metrics leave out, 2026-10-25. A trace begun in the page has no root span: its API calls are there side by side, but not how long the tap took to show its result. Wanted: the page reporting its tap as a span, the root of the trace its requests join.

Found reviewing what production's traces and metrics leave out, 2026-10-25. A trace begun in the page has no root span: its API calls are there side by side, but not how long the tap took to show its result. Wanted: the page reporting its tap as a span, the root of the trace its requests join.
rays added the enhancement label 2026-10-25 08:56:30 -07:00
Author
Owner

Fixed in dd91602: the page puts a root span id in each request's traceparent and reports the tap (ids, start, last answer) when the next begins or it is hidden; ipx builds the span with those ids through an id generator on the shared tracer provider (opentelemetry 0.33's span builder takes none). A test tap showed in Tempo as the root with its request under it. Deployed 2026-10-25.

Fixed in dd91602: the page puts a root span id in each request's traceparent and reports the tap (ids, start, last answer) when the next begins or it is hidden; ipx builds the span with those ids through an id generator on the shared tracer provider (opentelemetry 0.33's span builder takes none). A test tap showed in Tempo as the root with its request under it. Deployed 2026-10-25.
rays closed this issue 2026-10-25 09:35:56 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#376