OpenTelemetry in Next.js: traces that survive the edge/server boundary without losing context (opens in new tab)

OpenTelemetry in Next.js: traces that survive the edge/server boundary without losing context Why is observability in Next.js still a half-solved problem in 2025? We've had OpenTelemetry as the de facto backend standard for years — well documented in Spring Boot, plain Node, Go — and yet the App Router has a boundary that silently breaks trace context without raising a single visible error. I've wondered for a while if the community underestimates this because the problem doesn't throw except...