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

@rpc-bastion/observability

v0.4.1

Published

Event bus to OpenTelemetry (metrics + traces); Datadog via OTLP.

Readme

@rpc-bastion/observability

Bridge the RPC Bastion event bus to OpenTelemetry — metrics + traces, then out to Prometheus, Datadog, or any OTLP backend. No logging on the hot path; everything flows through the structured event bus.

Use it

import { createEventBus, registerOtelExporter } from '@rpc-bastion/observability';

const bus = createEventBus(); // re-exported from @rpc-bastion/core
const off = registerOtelExporter(bus, { prefix: 'bastion' });

// pass `bus` to createResilientRpc({ bus }) and createSender({ bus })
// ... later: off();

@opentelemetry/api is an optional peer dependency. Without an OTel SDK registered the exporter is a no-op — safe to call unconditionally. Register a NodeSDK with an OTLP exporter to start shipping data.

What it emits

  • Metrics: counters (rpc.requests, rpc.errors, rpc.retries, rpc.failovers, tx.submitted{route}, tx.rebroadcast, tx.route_fallback, tx.confirmed/tx.expired/tx.failed), histograms (rpc.latency, tx.confirmation_time), observable gauges (endpoint.health_score, endpoint.inflight, breaker.open_count).
  • Traces: a span tree per sendSmart (tx.send root → tx.attempt children per route, with route-fallback recorded). Per-RPC-call spans are off by default (volume).

Options

| Option | Default | Notes | |---|---|---| | meterProvider | global API | false disables metrics | | tracerProvider | global API | false disables traces | | prefix | none | prepended to every metric/span name | | scope | @rpc-bastion/observability | instrumentation scope |

Backends: Prometheus & Datadog

Point your OTel SDK's OTLP exporter at an OpenTelemetry Collector, which fans out to Prometheus (scrape) and Datadog (OTLP ingest) — one exporter, both backends, no dd-trace. A runnable docker-compose stack and configs are in docs/observability.md and docs/observability/.

Safety

The event bus isolates listeners: a throwing exporter never breaks the hot path or other listeners (it's routed to bus.onListenerError). The exporter also guards its own recorders, so observability can't affect transaction execution.