⇄ Sentry dataset field map

Map transactions/discover fields to spans/errors before the API cutoff

Local field-map fork. Not a Sentry SaaS. Not affiliated. Verify on Sentry Help Center.

LegacySpans / errors
transaction.duration|durationspan.duration
exclusive_timespan.self_time
transaction.statustrace.status
http.methodtransaction.method
url|http.urlrequest.url
titletransaction
platform.nameplatform
span.modulespan.category
geo.*user.geo.*
count()count(span.duration)
spm()epm()
percentile(transaction.duration,0.95)p95(span.duration)
(answer A + B)

How it works

  1. Pick the legacy dataset (including implicit default discover) and whether queries mix errors with transactions.
  2. Get a spans/errors field and function map, including is_transaction:true and discover-split guidance.
  3. Copy Markdown into the migration ticket — we never call Sentry APIs.

Sentry retires transactions, discover, and events datasets from Explore API queries on 2026-12-03. UI and SDKs are unaffected. Requests that omit dataset default to discover and are still impacted. Field renames such as transaction.duration→span.duration and function changes such as percentile→p95 are where migrations often still 400 after a naive dataset swap.

vs New Relic Synthetics Node22 / HubSpot validation fork: this is Explore dataset field mapping, not Synthetics runtime force-upgrade and not CRM pipeline validation.

Next: how-to · FAQ · use cases.