Post

some pretty cool things are coming for nuxt v5 + o11y 👀

@martindotnet.bsky.social

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.

Abdelrahman Awad

@awad.dev

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?

11/6/26, 5:18 pm0 reposts1 like

MartinDotNet

@martindotnet.bsky.social

11 June

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

Abdelrahman Awad

@awad.dev

11 June

Ah, I understand your concern now. Luckily, this isn't OTel 😁 it's a telemetry agnostic API. It doesn't produce telemetry on its own, the APM has to do it.

MartinDotNet

@martindotnet.bsky.social

11 June

I would assume that nuxt is producing a first part otel integration though? Based on this API. Thats the real value these days, not APM tools.

daniel r(ooooooh) in nyc 🇺🇸

@danielroe.dev

11 June

the idea would be that by emitting via tracing channel, you can easily 'catch' that data via an otel integration/plugin, but it's not opinionated tracing channels are agnostic and cross-runtime