Post

Please please please have the verbose off by default. So many tools are throwing all this on by default and it makes for a bad day 1 experience when you're part of a much wider system. Using this for local development, or if you're the only part of the ecosystem, is amazing though.

This PR is using tracing channels, the example shows every possible span when an APM subscribes to all channels. So by default, even if enabled, Nuxt won't emit anything unless an APM subscribes to every single channel, so I think the noise-control lever should exist there. Does that make sense?

I've assumed OpenTelemetry here, not APM tools. Maybe that isn't correct?

this is the perfect time to suggest changes! by ‘verbose’ you mean providing more information than just the event name …? the feature itself is opt-in …

I'm specifically referring to the number of spans and nesting. In node and express for instance, the default is to turn off middleware, turn off dns/net and fs because they're noise that doesn’t add value in the general usecase.

this is powered by tracing channels, supported in @nodejs.org, @deno.land, @bun.sh and @cloudflare.social workers! 👉 read more nodejs.org/api/diagnost... 👉 see github.com/unjs/untracing for a unified naming registry

thanks to @pi0.io for adding support in nitro/h3/srvx/unstorage, and for @awad.dev for suggesting we do the same in @nuxt.com 🙏