npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@zzazz/otel

v1.0.1

Published

OpenTelemetry SDK for NestJS/Node.js applications

Readme


This module provides an opinionated, plug-and-play wrapper around the OpenTelemetry Node SDK, specifically tailored for NestJS applications. It comes pre-configured with useful instrumentations like HTTP, Express, NestJS, TypeORM, and PostgreSQL.

📦 Installation

npm install @zzazz/otel

Or with yarn:

yarn add @zzazz/otel

Or with pnpm:

pnpm add @zzazz/otel

⚡ Quick Start

Import and initialize initOtel early in your app (before anything else)

// src/main.ts
import { initOtel } from '@zzazz/otel';

await initOtel({
  enabled: true,
  serviceName: 'my-nest-api',
  serviceVersion: '1.0.0',
  environment: 'production',
  endpoint: 'http://localhost:4318', // OTLP HTTP endpoint (collector)
  developerMode: false // keep it true for local development.
});

Then continue with your normal NestJS app bootstrap:

const app = await NestFactory.create(AppModule);
await app.listen(process.env.PORT || 3000);

⚙️ Configuration Options

| Option | Type | Default | Description | |---------------------|----------------------|---------------|-----------------------------------------------------------------------------| | enabled | boolean | true | Master toggle for enabling tracing | | serviceName | string | required | Your service name used in trace metadata | | serviceVersion | string | '1.0.0' | Optional version of your service | | environment | string | 'local' | Useful for tagging traces from different environments | | endpoint | string | required | OTLP HTTP collector endpoint (e.g., http://localhost:4318) | | developerMode | boolean | false | If true, uses ConsoleSpanExporter instead of OTLP (for local debugging) | | instrumentations | Instrumentation[] | Built-in set | Override or extend default instrumentations |

🧩 Built-in Instrumentations

By default, this SDK includes the following instrumentations:

  • @opentelemetry/instrumentation-http
  • @opentelemetry/instrumentation-express
  • @opentelemetry/instrumentation-nestjs-core
  • @opentelemetry/instrumentation-typeorm
  • @opentelemetry/instrumentation-pg

You can override them by passing a custom instrumentations array.

🧪 Developer Mode

Use developerMode: true to log all spans to the console (useful for local development without setting up a collector).

🔍 OTLP Collector Setup (Optional)

To collect traces locally, you can run an OpenTelemetry Collector:

docker run -p 4318:4318 otel/opentelemetry-collector-contrib:latest

Make sure the endpoint in your config points to this URL:

endpoint: 'http://localhost:4318'

🛑 Graceful Shutdown

The SDK listens for SIGINT, SIGTERM, and uncaughtException and automatically shuts down OpenTelemetry SDK and flushes spans.

Make sure the endpoint in your config points to this URL:

endpoint: 'http://localhost:4318'

📄 License

MIT