Pino transport

@squasher-ai/pino is a Pino transport. It sends your Pino logs to Squasher, and log lines at error level and above become issues. This page is tested with version 0.4.1 and Pino 10 on Node.js 26.

Install the transport

npm install @squasher-ai/pino pino

Add your ingest key and project ID to the environment of your service:

.env

SQUASHER_API_KEY=sq_pk_...
SQUASHER_PROJECT_ID=...

To get both values, see Create an ingest key.

Add the transport to your logger

Add @squasher-ai/pino as a transport target. This example also keeps the logs on standard output:

src/logger.ts

import pino from "pino";

export const logger = pino({
  transport: {
    targets: [
      { target: "pino/file", options: { destination: 1 } },
      {
        target: "@squasher-ai/pino",
        level: "info",
        options: {
          apiKey: process.env.SQUASHER_API_KEY,
          projectId: process.env.SQUASHER_PROJECT_ID,
          environment: process.env.NODE_ENV,
        },
      },
    ],
  },
});

level on the target sets the lowest level that goes to Squasher. Pino runs the transport in a worker thread, so pass only values that can be copied: strings, numbers, and plain objects. Set environment to production in production: automatic AI triage runs only on issues from that environment.

Log errors

Pass the error in the err field:

src/checkout.ts

import { logger } from "./logger";

try {
  await chargeCard(order);
} catch (err) {
  logger.error({ err, orderId: order.id }, "checkout failed");
}

The transport sends the event as checkout failed: <error message>, with the error type and the stack trace. Other fields, such as orderId, go into the event’s extra data. pid and hostname become tags.

Send a test error

Run this once with the same environment variables:

scripts/squasher-test.ts

import { logger } from "../src/logger";

logger.error({ err: new Error("Squasher test error") }, "test");

The transport sends events in batches, every 5 seconds or when 25 events are queued. Pino sends the rest when the process exits normally. Then select Issues in the sidebar of your project. If the error does not appear, see Troubleshooting.

Add spans, logs, and metrics

The package also exports the tracing helpers of the Cloudflare Workers SDK for Node.js. Call initSquasher once when the process starts:

src/index.ts

import { initSquasher, log, recordMetric, span } from "@squasher-ai/pino";

initSquasher({
  apiKey: process.env.SQUASHER_API_KEY!,
  projectId: process.env.SQUASHER_PROJECT_ID!,
  environment: process.env.NODE_ENV,
  resourceAttributes: { "service.name": "checkout-api" },
});

const orders = await span("db.query", { kind: "client" }, () => db.listOrders());
log.info("orders loaded", { count: orders.length });
recordMetric("orders.loaded", orders.length, { type: "counter" });

span sends one event when its function ends. When the function throws, the event has the error message and error level, and span throws the error again. The client sends events every 5 seconds and when the process exits normally. These helpers do not use the Pino transport or its options.

Options

These are the options of the transport target.

Option	Default	Description
`apiKey`	Required	Your ingest key. When it is empty or missing, the transport sends nothing.
`projectId`	Required	Your project ID.
`environment`	None	The environment name, for example `production`.
`release`	None	The release name, for example the git commit SHA.
`sampling`	Send all	Rates from 0 to 1: `successRate`, `errorRate`, `slowRate`, and `slowThresholdMs` (1000).
`batchSize`	`25`	The number of queued events that starts a send.
`flushIntervalMs`	`5000`	The longest time between sends, in milliseconds.
`maxRetries`	`3`	Retries after a network error or a retryable HTTP status.
`debug`	`false`	Log transport activity to the console. Debug mode does not sample.
`endpoint`	`https://ingest.squasher.ai`	The ingest URL.

Pino warn becomes warning, and trace becomes debug. sampling treats events at warning level and above as errors, so errorRate applies to them.

Limits

After an HTTP 401 response, the transport logs Invalid API key and stops sending for 60 seconds.
After an HTTP 429 response, the transport waits once and then drops the batch.
If the process ends with process.exit() or a crash, Pino can lose the events that are still in the worker thread.
Stack traces point at the files that Node.js runs. If you bundle your code, upload source maps for the release so the issue page shows the original files.

Give the setup to a coding agent

Copy this prompt into your coding agent to install the transport the same way:

Install @squasher-ai/pino in this Node.js service. In the Pino logger, add a transport target
"@squasher-ai/pino" next to the existing targets, with options apiKey from
process.env.SQUASHER_API_KEY, projectId from process.env.SQUASHER_PROJECT_ID, and environment from
process.env.NODE_ENV. Keep the existing log output. Log caught errors as logger.error({ err }, "message").
Verify with logger.error({ err: new Error("Squasher test error") }, "test").

Next steps

Node.js SDK

Capture uncaught exceptions and framework errors.

Design queryable logs

Choose log fields that are easy to search.

Winston transport

Send Winston logs instead.

Read AI triage

Learn what the triage summary tells you.

Get started

Guides

Install the transport

Add the transport to your logger

Log errors

Send a test error

Add spans, logs, and metrics

Options

Limits

Give the setup to a coding agent

Next steps

Node.js SDK

Design queryable logs

Winston transport

Read AI triage

​Install the transport

​Add the transport to your logger

​Log errors

​Send a test error

​Add spans, logs, and metrics

​Options

​Limits

​Give the setup to a coding agent

​Next steps

Node.js SDK

Design queryable logs

Winston transport

Read AI triage

Install the transport

Add the transport to your logger

Log errors

Send a test error

Add spans, logs, and metrics

Options

Limits

Give the setup to a coding agent

Next steps