Skip to content

docs: clarify that custom spans nest under request traces#3313

Merged
bartlomieju merged 1 commit into
mainfrom
docs/observability-custom-spans
Jun 18, 2026
Merged

docs: clarify that custom spans nest under request traces#3313
bartlomieju merged 1 commit into
mainfrom
docs/observability-custom-spans

Conversation

@bartlomieju

Copy link
Copy Markdown
Member

On the Observability
page, the Traces section explains the parent/child waterfall view but
never states that the Traces list itself only shows top-level request
traces. Users who add custom spans via manual instrumentation expect to
see them as standalone entries and get confused when they don't appear.

This adds a short clarification that custom spans show up as children
nested within the request trace they run under, and that you find them by
opening the relevant request trace. This matches the behavior a
maintainer confirmed in #2492.

Refs #2492. The remaining items in that issue (surfacing span events in
the dashboard, and traces for non-request contexts) are Deno Deploy
product behaviors rather than documentation changes.

The Traces list only shows top-level request traces, so custom spans
created via manual instrumentation appear as children inside the request
trace rather than as separate entries. Document this to avoid the
confusion reported in #2492.

Refs #2492
@bartlomieju
bartlomieju merged commit ae1d96e into main Jun 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant