What are the differences between MetinSeylan/Nestjs-OpenTelemetry and pragmaticivan/nestjs-otel?

[ruby fable]

• https://github.com/MetinSeylan/Nestjs-OpenTelemetry
• https://github.com/pragmaticivan/nestjs-otel

Curious to know how the 2 projects differ.

Nestjs-OpenTelemetry seems a bit easier to integrate, as it uses only a nestJS module, while nestjs-otel uses an external tracing.ts / instrumentation.ts + a module.

[ionic plover]

I'm not super familiar with the first, but nestjs-otel does not do any instrumentation that should be done by conventional opentelemetry library.

https://www.npmjs.com/package/@opentelemetry/instrumentation-nestjs-core

^ It expects you to use this instead because as nestjs evolves, the opentelemetry will support it natively.

There's also a known problem when you don't do the instrumentation before NestJS start. The dependency tree is not able to enforce opentelemetry as the first package to be load, and you would actually want that to be the first thing before you import any library.

By using the method where you import instrumentation as the first thing, now you get a lot of auto instrumentation for many known nodejs libraries with https://www.npmjs.com/package/@opentelemetry/auto-instrumentations-node

I see it also says open telemetry metric SDK is not stable, but it is stable here: https://github.com/open-telemetry/opentelemetry-js

I do suggest you investigate both though, I can't point out differences as I've only used one of them in production 😹

[ruby fable]

Thanks for the detailed answer! 🙂