Ensure http.client and http.server spans emit low-cardinality span names when span streaming is enabled. Span name rules: [https://getsentry.github.io/sentry-conventions/names/#http](<https://getsentry.github.io/sentry-conventions/names/#http>) Fallback constant: `HTTP_SPAN_NAME_FALLBACK` in `packages/core/src/tracing/spans/spanNames.ts` Part of getsentry/sentry-javascript#22350 — remember to check `traceLifecycle` and keep the existing name for `static` mode.
Activity
linear-code commentedon Aug 24, 2026
JS-3412
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
docs(migration): Document low-cardinality http.server span names
feat(core): Emit low-cardinality http.server span names when streaming (
feat: Emit low-cardinality http.server span names in framework SDKs (#…
docs(migration): Document low-cardinality http.server span names (#23598
feat: Resolve relative outgoing-request URLs to the page domain
feat: Emit low-cardinality http.client span names for fetch and XHR (#…
feat: Emit low-cardinality http.client span names for node:http and u…
github-actions commentedon Sep 23, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #23598, which was included in the 11.0.0 release.