David Luna

@djMax thanks on [answering](https://github.com/open-telemetry/opentelemetry-js/discussions/3346#discussioncomment-7856374) on the question about donating the implementation of https://github.com/gas-buddy/service/blob/main/src/telemetry/fetchInstrumentation.ts to this repo. This is the issue we're using to track it's progress. As discussed in the...

Link to the contrib PR: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1951

Contrib repo migrated to use `npm workspaces` in https://github.com/open-telemetry/opentelemetry-js-contrib/pull/1771 for package management and still using `lerna` for publishing. Is that an option?

There is a new instrumentation released a couple of weeks ago. This instrumentation works for `undici` but also for the `fetch` global Node.js API (since the API uses undici under...

Closing the issue. @ehtb ping me or open a new issue if needed :)

With `v7.2.5` the error was not reported so you could load all files separately. ```js const {load} = require('protobufjs'); load( [ `${__dirname}/org/common/common.proto`, `${__dirname}/org/test/test.proto` ], (err, root) => { if (err)...

> To summarize: I like the full overrides, as it's (IMO) the easiest to understand option. Once there is a statement from the Spec SIG that this overriding the User-Agent...

Hi, I've had a similar issue in a project and we came with a couple of ways to avoid this error 1. add `DOM` to the lib compiler option https://www.typescriptlang.org/tsconfig#lib...

Just came across this issue and did some test to see if still apply. Mongoose is added to the support list in `elastic-apm-agent@4` This new version does not support node

@JamieDanielson I've added your suggestion. Thanks :)