Issue
In a trace, custom data (attributes or additional data) appears on individual spans but not on the transaction. This is common with JavaScript SDK v8 and OpenTelemetry-based Node SDKs.
Applies To
All SaaS Customers and Self-Hosted Users
Tracing
JavaScript SDKs
Resolution
Sentry stores and displays that data on spans, not on the transaction.
In JavaScript SDK v8 and later (and recent v7 Node SDKs), tracing is span-based and OpenTelemetry-backed. Transactions are no longer a separate SDK object. The UI may still group spans under a transaction, but attributes stay on the span you set them on. They are not copied to the root span.
Open the trace waterfall and select the span that should have the data. Check that span’s attributes.
Query the data in Explore → Traces, not on the transaction summary.
Attach new data with
span.setAttribute(orattributesonSentry.startSpan). Do not expectsetExtra/ additional data on the transaction.
See the v8 tracing API changes for the span model.