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

logd-opentelemetry

v1.0.1

Published

Forward logd messages to the OpenTelemetry Logs API without replacing existing sinks.

Readme

logd-opentelemetry

Forward logd messages to the OpenTelemetry Logs API without replacing other sinks or initializing a LoggerProvider.

Peer dependencies: logd ≥ 5.4 (for addLogSink / removeLogSink), @opentelemetry/api, @opentelemetry/api-logs.

Dev: from the pnpm workspace root, pnpm test in lib/logd-opentelemetry runs section-tests with coverage (see section-tests Coverage); artifacts under coverage/.

Install

npm install logd-opentelemetry @opentelemetry/api @opentelemetry/api-logs logd

Usage

Your application or SDK must obtain an OpenTelemetry Logger from its own provider, then register this adapter once:

import { logs } from '@opentelemetry/api-logs';
import logd from 'logd';
import { registerOtelSink, unregisterOtelSink } from 'logd-opentelemetry';

const otelLogger = logs.getLogger('my-service', '1.0.0');

registerOtelSink(logd, {
  otelLogger,
  // sinkId: 'logd-opentelemetry', // default
});

Teardown (removes only this named sink; does not shut down the provider):

unregisterOtelSink(logd);

Multiple sinks

registerOtelSink uses logd.addLogSink with a unique id (sinkId, default logd-opentelemetry). Other code can call addLogSink for unrelated sinks; each receives every LogMessage without knowing the others.

  • Second registration with the same sinkId throws (same as logd). Use unregisterOtelSink first or pass force: true to replace only this adapter’s registration.
  • Legacy registerLogSink on the same instance is unchanged: OTel is an extra named sink and does not replace it.

Behavior

  • Structured body: one argument is serialized as one structured value; multiple arguments become { parts: [...] } (not a single concatenated string).

  • Errors: serialized with name, message, stack, and optional cause.

  • Unsafe values: circular references and other edge cases are handled without throwing out of the sink.

  • Severity: mapped from logd’s level to SeverityNumber / severityText.

  • Attributes: logd.module, logd.level, logd.level_value; semantic code.filepath, code.lineno, code.function when callsite exists (Node).

  • Trace: LogRecord.context is set to context.active() at emit time so the SDK can correlate with the current span when present.

    @opentelemetry/api ships a no-op ContextManager by default, so context.with(...) does not propagate the active span until the host registers a real manager (for Node, typically @opentelemetry/context-async-hooks) via context.setGlobalContextManager(...). Without that, correlation still works if the Logs SDK reads context another way — but for standard async propagation, install the async-hooks context manager in the app/SDK startup.

  • Runtime: only calls otelLogger.emit. No exporters or provider initialization in this package.

API

| Export | Description | |--------|-------------| | registerOtelSink(host, options) | Attach sink via host.addLogSink (typically logd). | | unregisterOtelSink(host, sinkId?) | host.removeLogSink(sinkId ?? default). | | toSerializable(value, options?) | Optional reuse of the structured serializer. |

License

MIT