Open 2nPlusOne opened 3 months ago
I assume that you want to track queries happening on the server here, not what's happening in the user's browser?
useQuery
doesn't make any api requests during SSR. Next.js will only let you do one render, so you'd only get a loading state in SSR, no matter if a request were made or not.
If you want to make requests and have the results rendered during SSR, you'll have to use the useSuspenseQuery
hook, because that one will pause React rendering until the request is done and stream the result to the browser.
Howdy,
My team and I have been using the experimental package for a few months now as we build up our Next.js 14 app. It's been working quite well! However, we recently started to implement telemetry, and have ran into some issues related to the package.
What works
We followed the guide on the blog, and were able to get telemetry working for queries called from the server.
As expected, when a query is made using
getClient().query
, the query traces show up on the Jaeger UI, and the context progagates properly to the backend service.What doesn't work
When making queries from the client using
useQuery
from the experimental package, the traces do not show up on Jaeger.