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

@salesdeskpro/apm-service

v0.2.0

Published

Standalone APM collector — Dynatrace-style logs, metrics, and traces for any Node service

Readme

@salesdeskpro/apm-service

Standalone APM collector — Dynatrace-style central backend for logs, metrics, and distributed traces.

Any Node.js service installs @salesdeskpro/apm-agent and points at this service. No observability code inside your business apps beyond one middleware line.

Architecture

┌─────────────┐   POST /v1/ingest/http    ┌──────────────────┐
│ billing-api │ ─────────────────────────►│                  │
└─────────────┘                           │  apm-service     │
┌─────────────┐   X-APM-Key               │  (PostgreSQL)    │◄── UI / CRM
│ email-api   │ ─────────────────────────►│                  │
└─────────────┘                           └──────────────────┘
┌─────────────┐
│ worker      │ ─────────────────────────►
└─────────────┘

Quick start

cd apm-service
cp .env.example .env
# edit DATABASE_URL + APM_API_KEYS
npm install
npm start

Open http://localhost:9090 for the built-in console (set API key in the page).

Environment

| Variable | Description | |----------|-------------| | PORT | HTTP port (default 9090) | | DATABASE_URL | PostgreSQL connection string | | APM_API_KEYS | Comma-separated ingest + read keys | | APM_SLOW_SPAN_MS | Slow trace threshold (default 500) | | CORS_ORIGINS | UI origins (* for dev) |

API

Ingest (agent → collector)

POST /v1/ingest/http — header X-APM-Key

{
  "serviceName": "billing-api",
  "tenantId": "acme",
  "traceId": "…",
  "spanId": "…",
  "routePattern": "GET /api/invoices",
  "method": "GET",
  "statusCode": 200,
  "durationMs": 42,
  "level": "INFO"
}

POST /v1/ingest/batch — custom logs + spans batch.

Query (UI / tools)

| Endpoint | Description | |----------|-------------| | GET /v1/status | Health + schema | | GET /v1/services?tenantId= | Services reporting for tenant | | GET /v1/tenants/:tenantId/logs | Log stream | | GET /v1/tenants/:tenantId/metrics | Aggregated metrics | | GET /v1/tenants/:tenantId/traces | Distributed traces |

All query routes require X-APM-Key.

Query params: service, days, limit, level, search (logs).

Wire a Node service

See packages/apm-agent/README.md.

APM_SERVER_URL=https://apm.yourcompany.com
APM_API_KEY=your-key
APM_SERVICE_NAME=my-service

Wire SalesDesk CRM

API (email-api/.env):

APM_SERVER_URL=https://apm.yourcompany.com
APM_API_KEY=your-key
APM_SERVICE_NAME=email-api

UI (.env):

VITE_APM_ENABLED=true
VITE_APM_SERVICE_URL=https://apm.yourcompany.com
VITE_APM_READ_KEY=your-key

Embedded APM_ENABLED plugin is not used when APM_SERVER_URL is set.

Deploy

  • Run as its own Cloud Run / container / VM
  • Dedicated Postgres (recommended) or separate DB
  • Put behind HTTPS; rotate APM_API_KEYS

Disable

Stop the service — your apps keep running; agent logs warnings only.