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

@grammyjs/opentelemetry

v0.1.0

Published

grammY plugin that adds OpenTelemetry tracing to your bot

Readme

grammY OpenTelemetry

Integrates OpenTelemetry into grammY.

Development is in progress.

Description

After a lot of thought and research, we came to the conclusion that it would be bad to integrate with a particular technology, especially if it is possible to support many at once. Fortunately, there is the OpenTelemetry project, which defines a single approach to collecting and managing telemetry that integrates perfectly with many existing services. However, there are some problems with it:

  1. The JS toolkit is quite young, so many things are experimental or just under development, which makes it difficult to use.
  2. They split the Web and Node.js tools into separate packages, which will cause support issues in the future.
  3. They are very fond of autoinstrumentation, which intercepts require/import calls and patches the requested package, which we think is a very, very bad pattern that we don't want to impose on grammY users.

This plugin allows you to use OpenTelemetry without those caveats.

Installation

Node.js:

npm install grammy @grammyjs/opentelemetry

Deno:

deno add npm:grammy npm:@grammyjs/opentelemetry

Setup

import { Bot, type Context } from "grammy";
import { openTelemetry, type OpenTelemetryContext, traced } from "@grammyjs/opentelemetry";

const bot = new Bot<Context & OpenTelemetryContext>("token");
bot.use(openTelemetry("my-bot"));

To use a custom tracer:

bot.use(openTelemetry("my-bot", { tracer: customTracer }));

Events

event() emits an OpenTelemetry Log Event:

bot.command("start", (ctx) => {
  ctx.telemetry.event("command.start", { "user.id": ctx.from?.id });
});

Traces

Run work inside a child span of the current update:

bot.command("start", async (ctx) => {
  await ctx.telemetry.trace(
    "command.start",
    { command: "start" },
    async (span) => {
      span.addEvent("command.start.handle");
      await ctx.reply("Hello! I'm a bot!");
    },
  );
});

traced() provides the same lifecycle as grammY middleware:

bot.command(
  "start",
  traced(
    "command.start",
    { command: "start" },
    async (ctx, span) => {
      span.addEvent("command.start.handle");
      await ctx.reply("Hello! I'm a bot!");
    },
  ),
);

Manual spans

Custom spans can be added manually:

bot.command("finish", async (ctx) => {
  const span = ctx.telemetry.start("command.finish", { success: true });
  try {
    span.setAttribute("telegram.chat.id", ctx.chat.id);
    await ctx.reply("Finished!");
  } finally {
    span.end();
  }
});

[!NOTE]

start() returns a DisposableSpan. It supports using, which ends the span automatically when execution leaves its scope:

using span = ctx.telemetry.start("command.finish", { success: true });

Typed telemetry

You can type event and span attributes by defining maps from their names to their attributes. If you omit a map, that signal accepts any name and attributes.

import { Bot, type Context } from "grammy";
import { openTelemetry, type OpenTelemetryContext, traced } from "@grammyjs/opentelemetry";

type BotEvents = {
  "command.start": {
    "user.id"?: number;
  };
};

type BotSpans = {
  "command.start.reply": {
    "user.id"?: number;
  };
  "command.finish": {
    success: boolean;
  };
};

type BotContext = Context & OpenTelemetryContext<BotSpans, BotEvents>;

const bot = new Bot<BotContext>("token");
bot.use(openTelemetry<BotSpans, BotEvents>("my-bot"));

bot.command("start", async (ctx) => {
  ctx.telemetry.event("command.start", { "user.id": ctx.from?.id });

  await ctx.telemetry.trace(
    "command.start.reply",
    { "user.id": ctx.from?.id },
    async (span) => {
      const message = await ctx.reply("Hello!");
      span.setAttribute("telegram.message.id", message.message_id);
    },
  );

  // Type error: "command.unknown" is not defined in BotEvents.
  ctx.telemetry.event("command.unknown", {});

  // Type error: "command.start" events require a numeric "user.id".
  ctx.telemetry.event("command.start", { "user.id": "123" });

  // Type error: "command.unknown" is not defined in BotSpans.
  ctx.telemetry.start("command.unknown", {});

  // Type error: "command.finish" spans require "success".
  ctx.telemetry.start("command.finish", {});

  // Type error: "user.id" must be a number.
  await ctx.telemetry.trace(
    "command.start.reply",
    { "user.id": "123" },
    async (span) => {
      span.addEvent("reply.started");
      await ctx.reply("Hello!");
    },
  );
});

// Type error: "command.finish" requires attributes before the callback.
bot.command(
  "finish",
  traced("command.finish", async (ctx) => {
    await ctx.reply("Finished!");
  }),
);