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

@queuebert/otel

v0.0.1

Published

OpenTelemetry helper utilities and NestJS integration helpers for Queuebert queue metrics.

Readme

@queuebert/otel

OpenTelemetry metrics and Queuebert snapshot helpers for BullMQ applications.

The package records counters, duration histograms, and observable queue gauges through an application-owned OpenTelemetry Meter. It does not start an SDK, choose an exporter, open a Prometheus endpoint, or install third-party BullMQ auto-instrumentation.

Installation

npm install @queuebert/otel @opentelemetry/api

Install the Nest peers when using the Nest integration:

npm install @queuebert/otel @queuebert/nest @nestjs/bullmq @nestjs/common @nestjs/core bullmq @opentelemetry/api

Configure your OpenTelemetry SDK before importing application code, then pass its meter to Queuebert. The global API meter is also used automatically when a meter is not supplied.

Framework-agnostic usage

import { metrics } from '@opentelemetry/api';
import { createResourceAttributes, MetricsRegistry } from '@queuebert/otel';

const registry = new MetricsRegistry(
  {
    durationBuckets: [10, 50, 100, 500, 1000, 5000],
    perJobNameMetrics: true,
    maxJobNames: 100,
  },
  metrics.getMeter('email-worker.queuebert', '1.0.0'),
  createResourceAttributes({
    serviceName: 'email-worker',
    deploymentEnvironment: 'production',
  }),
);

registry.recordJobCompleted('emails', 'welcome', 82);
registry.recordJobFailed('emails', 'digest', 410);
registry.updateQueueCounts('emails', {
  waiting: 12,
  active: 2,
  completed: 240,
  failed: 4,
  delayed: 1,
});

const snapshot = registry.getSnapshot();
const queuebertStats = registry.transformToQueuebertStats('emails');

Call registry.destroy() during shutdown to unregister observable callbacks.

NestJS module

import { Module } from '@nestjs/common';
import { QueuebertOTelModule } from '@queuebert/otel/nest';

@Module({
  imports: [
    QueuebertOTelModule.forRoot({
      instrumentationName: 'email-worker.queuebert',
      instrumentationVersion: '1.0.0',
      resource: {
        serviceName: 'email-worker',
        deploymentEnvironment: 'production',
      },
    }),
  ],
})
export class AppModule {}

QueuebertOTelService exposes recordJobCompleted, recordJobFailed, updateQueueCounts, Queuebert-shaped snapshots, and the configured Meter and Tracer. The same instances are injectable with QUEUEBERT_OTEL_METER and QUEUEBERT_OTEL_TRACER.

Async module configuration is supported through QueuebertOTelModule.forRootAsync().

Metrics

The stable metric names are exported as METRIC_NAMES:

  • queuebert.job.completed
  • queuebert.job.failed
  • queuebert.job.duration
  • queuebert.job.waiting
  • queuebert.job.active
  • queuebert.job.delayed
  • queuebert.queue.throughput

Job-name cardinality is bounded by maxJobNames; overflow names are aggregated under __other__. Failure and success rates are fractions from 0 to 1.