My bad, this is open telemetry stuff to check the status of your servers, not for vendors to extract as much data as they can from you.
> I'm trying to find how they implemented the "use workflow" thing, and before I could find it I already found https://github.com/vercel/workflow/blob/main/packages/core/s...
> Telemetry is part of the core.
> Yuck.
It's on the landing page, there is not even a standalone mode yet, so you can't use it with node.js you need to use with Next.js. All to say, it's just early alpha preview, I would wait the project to mature before considering using it anywhere.
My bad, this is open telemetry stuff to check the status of your servers, not for the vendor to slurp as much data from you as possible.
This is Open Telemetry functions you're referencing. Being able to trace, profile and debug your own code that's executing in a highly distributed environment is a pretty useful thing. This isn't (necessarily) user behavior telemetry.
At least understand what you're looking at before getting the ick.
That's fair. I'm too accustomed to seeing the other type of telemetry shoved in all over the place.
Good luck running a server without any sort of telemetry. How will you debug stuff without logs and traces? Seems to me that the priorities are with practical, real everyday engineering concerns.
It’s apparently an swc compiler plugin.