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
Name `handler` spans after the route they serve when span streaming is
enabled, or `Request handler` if no route set. Static mode left as is.
Drop Fastify and Hapi method, as the template dictates. NestJS and
Elysia resolve no route when the span starts. The NestJS callback name
stays on `nestjs.callback`. Elysia callback name is added to
`code.function.name`, so no information is lost by removing it from the
span name.
Also: correct `REQUEST_HANDLER_SPAN_NAME_FALLBACK`: the conventions
spell the fallback `Request handler`, and its `@see` link pointed at the
resource section.
closes#23533
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|`pageload`| The parameterized route, or the raw URL path if the SDK couldn't resolve one (`/users/123`) | The parameterized route, or `Pageload` if the SDK has none |
629
629
|`router`| Framework-specific, sometimes containing the raw URL (`/users/123`, `SvelteKit Route Change`) | The span's `http.route`, or `Router` if the SDK has none |
630
+
|`handler`| Framework-specific, often carrying the request method (`GET /users/:id`, `route-handler`, `getUser`) | The span's `http.route`, or `Request handler` if the SDK has none |
630
631
|`graphql`| The graphql phase and, for operations, the operation name (`query GetUser`, `graphql.parse`, `graphql.resolve user.0.name`) | The operation type, or the processing type where there is none (`GraphQL query`, `GraphQL parse`, `GraphQL resolve`) |
631
632
|`resource.*`| The resource URL, relative to the page origin for same-origin resources (`/assets/app.js`) | The resource domain (`cdn.example.com`), or `Resource` if the SDK has none |
632
633
@@ -642,6 +643,8 @@ For the same reason, `useOperationNameForRootSpan` no longer renames the enclosi
642
643
643
644
Only the Express, Koa and Hapi integrations resolve a route template for `router` spans. Angular, Ember and SvelteKit have none when the span starts, so their router spans are named `Router`.
644
645
646
+
Only the Express, Fastify and Hapi integrations resolve a route template for `handler` spans. NestJS and Elysia have none when the span starts, so their request handler spans are named `Request handler`. The handler function name stays on an attribute: `nestjs.callback` for NestJS, and `code.function.name` for Elysia, which now sets it on every lifecycle handler span.
647
+
645
648
Child spans of a service or root span carry its name in their `sentry.segment.name` attribute, so that changes with it. If you group or filter spans by segment name in dashboards or alerts, update those references.
646
649
647
650
`ignoreSpans` is evaluated when a span **starts**, at which point a span might not yet have its final name. For example, an unresolved pageload span name is named `'Pageload'` and might receive its final, resolved route name later.
0 commit comments