testing-nestjs VS opentelemetry-js

Compare testing-nestjs vs opentelemetry-js and see what are their differences.


A repository to show off to the community methods of testing NestJS including Unit Tests, Integration Tests, E2E Tests, pipes, filters, interceptors, GraphQL, Mongo, TypeORM, and more! (by jmcdo29)
Our great sponsors
  • Sonar - Write Clean JavaScript Code. Always.
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • Scout APM - Truly a developer’s best friend
  • Zigi - Delete the most useless function ever: context switching.
testing-nestjs opentelemetry-js
7 10
2,093 1,571
- 6.3%
6.9 9.6
3 days ago 2 days ago
TypeScript TypeScript
MIT License Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of testing-nestjs. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-13.


Posts with mentions or reviews of opentelemetry-js. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-11.
  • Logs and tracing: not just for production, local development too
    4 projects | news.ycombinator.com | 11 Nov 2021
    4. Register automatic instrumentations. For example, you can automatically trace all XHR requests, fetch requests, page loads, and user interactions. With distributed tracing, you should always prefer automatic instrumentation whenever possible to reduce maintenance and leverage existing conventions. The document load instrumentation allows you to treat the server as the parent span to a given page load, from which the client will then be the root span to everything in the server. This is an extremely powerful concept that allows traces to viewed from the perspective of the user, encapsulating all requests and user interactions in a single trace with no manual instrumentation!

    We also trialed Sentry's APM tool (also marketed as a distributed tracing tool). While it had pretty charts, dashboards, niceties like core web vitals, and integrated well with Sentry's error product, its utility as a distributed tracing tool is significantly less powerful than tools like Honeycomb. You will end up using a large amount of your user's bandwidth sending telemetry data that can't fully be leveraged in the Sentry UI. When I last used (in April 2021), the spans of a given trace could only be viewed in a specific part the UI and they couldn't be searched for in queries or used in charts. I'm unsure if this has been updated. But this is not the worse part. Because Sentry uses its own data model for traces, it is not compatible with open source standards such as OpenTelemetry or OpenTracing! The sales team will not tell you this during the trial. This means our entire backend, which was already instrumented with OpenTracing, would now also need to instrument Sentry's tracing (...if they supported the language) in order to connect frontend traces to backend traces. Each team I met with their sales team, I said the same thing: support OpenTelemetry, otherwise you are asking for us to further isolate our backend and frontend teams.

    It looks like they have heard this opinion, as they have recently published a blog post about the evolution of the distributed tracing API, citing incompatibility with OpenTelemetry due to their data model. It will require a very large change for them to support this. Meanwhile, OpenTelemetry can be used with any tracing vendor, a large number of languages, the other major instrumentation standards (OpenTracing, OpenCensus), and any trace propagation format.

    - [1]: https://github.com/open-telemetry/opentelemetry-js

  • Monitoring consumer lag in Azure Event Hub
    2 projects | dev.to | 30 Sep 2021
    Consumer lag will quickly show any functional or technical issue with your event stream. By using the code examples from this blogpost, you can avoid having to dive into the SDKs yourself. Of course, you can adopt the metric collection to send the metric to the logs or to another metrics system like prometheus, datadog, or open telemetry.
  • Any good tutorial showing you which library to use for dependency injection in a project?
    9 projects | reddit.com/r/node | 29 Aug 2021
    I would work on getting Open Telemetry pointed at an “all-in-one” Jaegar instance and move on from there: https://www.jaegertracing.io/docs/1.25/getting-started/ https://github.com/open-telemetry/opentelemetry-js Various cloud providers may have a way to collect/view traces as well, but, Jaegar and the Open Telemetry Collector are the open source way to do that. The projects are in the process of converging in some ways — everything is in flux.
  • Distributed Tracing 101 for Full Stack Developers
    3 projects | dev.to | 12 Aug 2021
    OpenTelemetry is a collection of open source tools, APIs, and SDKs for instrumenting, generating, and exporting telemetry data from running software. It provides language-specific implementations for most popular programming languages, including both browser JavaScript and Node.js.
  • OpenTelemetry kafkajs instrumentation for Node.js
    3 projects | reddit.com/r/apachekafka | 5 Aug 2021
    Compatible with SDK v0.24.0
  • Running Jaeger Locally: How to Get Started
    4 projects | dev.to | 8 Jul 2021
    If you are writing a new instrumentation library, observing the tracing output in a UI can be much easier than browsing through textual logs. You can browse the JS instrumentation package for more info and examples.
  • Setting up application monitoring for your Nodejs app in 20 mins with open source solution
    3 projects | dev.to | 8 Jun 2021
    SigNoz supports OpenTelemetry as the primary way for users to instrument their application. OpenTelemetry is a single, vendor-agnostic instrumentation library per language with support for both automatic and manual instrumentation. You don't need to worry about instrumentation in this tutorial. OpenTelemetry comes with all currently available instrumentation.
  • OpenTelemetry KafkaJS Instrumentation for Node.js
    2 projects | dev.to | 10 Mar 2021
    OpenTelemetry is a CNCF project, which, among other things, enables the collection of distributed traces.
  • Launch HN: SigNoz (YC W21) – open-source alternative to DataDog
    3 projects | news.ycombinator.com | 9 Feb 2021
    You make an interesting point. That is actually something we are constantly asked by our users. I guess our approach would be to prioritise developing of integrations based on community demand, and as we mature as a project - we would possibly have integrations contributed by community also.

    Though one thing which is making things a bit simpler for us is the increasing maturity of opentelemetry ( https://opentelemetry.io/ ) It is an instrumentation library which supports many languages and frameworks, and by supporting Opentelemetry we get at least instrumentation for many languages and framework in one go.

What are some alternatives?

When comparing testing-nestjs and opentelemetry-js you can also consider the following projects:

Sentry - Developer-first error tracking and performance monitoring

prom-client - Prometheus client for node.js

microservice-template - 📖 Nest.js based microservice repository template

nest-queue - The queue package for your NestJS Applications

axios-auth-refresh - Library that helps you implement automatic refresh of authorization via axios interceptors. You can easily intercept the original request when it fails, refresh the authorization and continue with the original request, without user even noticing.

signoz - SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool

nestjs-commander - A module for using NestJS to build up CLI applications

PostHog - 🦔 PostHog provides open-source product analytics, session recording, feature flagging and a/b testing that you can self-host.

f1-telemetry-client - A Node UDP client and telemetry parser for Codemaster's Formula 1 series of games

InversifyJS - A powerful and lightweight inversion of control container for JavaScript & Node.js apps powered by TypeScript.

fastify-preact-ssr - Fastify server-side renders Preact to html and serves with a Preact client.js bundle for DOM hydration.

opentelemetry-specification - Specifications for OpenTelemetry