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

@lndr/opentelemetry-typescript

v1.1.6

Published

Boilerplate for OpenTelemetry instrumentation.

Downloads

629

Readme

opentelemetry-typescript

Boilerplate for OpenTelemetry instrumentation.

Getting started:

The first step is to instrument your application code with OpenTelemetry and send its metrics, traces, and logs to the OpenTelemetry collector.

For this example, we will use the OTLP HTTP exporters:

npm install @opentelemetry/exporter-metrics-otlp-http @opentelemetry/exporter-trace-otlp-http @opentelemetry/exporter-logs-otlp-http
// ./instrumentation.js
const OpenTelemetry = require('@lndr/opentelemetry-typescript');
const { OTLPMetricExporter } = require('@opentelemetry/exporter-metrics-otlp-http');
const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-http');
const { OTLPLogExporter } = require('@opentelemetry/exporter-logs-otlp-http');

OpenTelemetry(
	'my-app:1.0.0',
	{
		exporters: {
			metrics: [
				new OTLPMetricExporter({ url: `http://localhost:4318/v1/metrics` })
			],
			traces: [
				new OTLPTraceExporter({ url: `http://localhost:4318/v1/traces` })
			],
			logs: [
				new OTLPLogExporter({ url: `http://localhost:4318/v1/logs` })
			]
		}
	}
).start();

Then you can run your Node.js application by preloading the instrumentation file, like below:

node -r ./instrumentation.js my-app.js

You can use other available exporters, just remember to install them in your project first.

Infrastructure setup:

After your code is instrumented, the next step is to spin up the OpenTelemetry collector and the LGTM stack (Loki, Grafana, Tempo and Mimir).

If you need instructions for configuring your deployment, refer to the examples in Grafana’s intro-to-mltp repository or the official Grafana Labs documentation.


Notice

This project, opentelemetry-typescript, makes use of the OpenTelemetry packages published under the Apache License 2.0.

This package itself is licensed under the MIT license.

Disclaimer: This project is provided “as is”, without warranty of any kind. The author assumes no responsibility for how this package is used.