Richard Simpson

This is much belated, but would this project be amenable to adding a workerd (e.g. Cloudflare) export platform implementation? With a recent change they've made, it should be possible to...

I can confirm that I get the same issue/error when using the latest version of the Vite react-swc plugin.

Sampling that works both in the broad context of a span's outcome (tail-based sampling) and spans part (is this span or sub-span interesting?) would be an awesome way to cut...

I think it's still worth have an "agent" in a layer to take advantage of things like the Telemetry API and handling batch. That said, that agent doesn't necessarily need...

Bump. As far as I'm aware, this issue hasn't been resolved even with the introduction of the new lambda repo.

I'm not sure why either to be honest. We're doing a pretty bog standard fetch: https://github.com/RichiCoder1/opentelemetry-sdk-workers/blob/main/packages/opentelemetry-sdk-workers/src/exporters/OTLPCloudflareExporterBase.ts#L103. I could try logging out more details about the specific error to maybe surface...

It's not a full fix since fetch is kind of opaque, but I'm updating the error message to at least hint it might be an export url issue.

> @Schachte I struggled to debug the port issue on a different project as well, but it is documented at [developers.cloudflare.com/workers/platform/known-issues/#custom-ports](https://developers.cloudflare.com/workers/platform/known-issues/#custom-ports) Wow, I actually did not know that! I'll see...

@dmitry-shibanov apologies for not seeing that closed ticket! I very much hope ya'll do. While technically experimental, it's being officially recommended and there's no (current) way to use both this...

The semi-simple way w/ caching and something like pnpm would be: ```yaml - run: corepack enable - uses: actions/setup-node@v3 with: node-version: 16 cache: pnpm - run: pnpm i ``` I...