Not getting http.server spans in Next.js server components

[landenai]

Environment

• Vercel Production Deployment
  
• Github

Steps to Reproduce:

• load vercel deployment of products page (https://empower-omega-eight.vercel.app/products)
• This routes to a server component
• wait a few minutes
• refresh the products page
• Observer trace data in Sentry https://demo.sentry.io/traces/?project=4508162424176640&statsPeriod=3m

Expected Result:

• We see two separate /products pageload traces with http.server spans

Actual Result:

• After step a), we see a /products pageload trace with no http.server spans (like this)
• When you reload the page, the original trace gets “enriched” with the server spans (like this). There is an additional trace with the same time stamp and a http.server span at the root (example).
• There is also a trace for the second /products pageload without http.server spans (this may take a few moments to appear). If you were to refresh a third time, this trace would get “enriched” with server spans and the cycle would continue

[lforst]

Theory is that serverside trace data isn't flushed properly on Vercel.