Logging

evmPortalStream() accepts a Pino-compatible logger, so you can route pipeline logs to any Pino transport — GCP Cloud Logging, Sentry, or a local pretty-printer. Configure it once on the source; every transformer and target then receives the same instance as ctx.logger.

Basic custom logger

Build a Pino transport, pass pino(transport) as the source’s logger, and the whole pipeline logs through it:

import { createTarget } from "@subsquid/pipes";
import { commonAbis, evmEventDecoder, evmPortalStream } from "@subsquid/pipes/evm";
import pino from "pino";

async function main() {
  const transport = pino.transport({
    target: "pino-pretty",
    options: {
      colorize: true,
      translateTime: "HH:MM:ss",
    },
  });

  const source = evmPortalStream({
    id: "custom-logging",
    portal: "https://portal.sqd.dev/datasets/ethereum-mainnet",
    outputs: evmEventDecoder({
      range: { from: "latest" },
      events: { transfers: commonAbis.erc20.events.Transfer },
    }).pipe(({ transfers }) => transfers),
    logger: pino(transport),
  });

  await source.pipeTo(
    createTarget({
      write: async ({ logger, read }) => {
        for await (const { data } of read()) {
          logger.info({ count: data.length }, "Processed batch");
        }
      },
    }),
  );
}

void main()

Cloud transports

Only the transport changes per destination — the rest of the pipe above stays the same. Build the transport, then pass pino(transport) as the source logger.

GCP Cloud Logging
Sentry
Multiple transports

const transport = pino.transport({
  target: "@google-cloud/logging-pino",
  options: {
    projectId: "your-project-id",
    logName: "pipes-indexer",
  },
});

Route only errors to Sentry, and wrap the write loop so failures surface as logger.error:

const transport = pino.transport({
  target: "pino-sentry-transport",
  options: {
    sentry: { dsn: process.env.SENTRY_DSN, environment: "production" },
    level: "error", // only forward errors to Sentry
  },
});

Fan out to several destinations at once, each with its own level:

const transport = pino.transport({
  targets: [
    { target: "pino-pretty", options: { colorize: true }, level: "info" },
    { target: "@google-cloud/logging-pino", options: { projectId: "your-project-id" }, level: "info" },
    { target: "pino-sentry-transport", options: { sentry: { dsn: process.env.SENTRY_DSN } }, level: "error" },
  ],
});

The ctx.logger in transformers and targets is the same logger instance passed to the source. Configure logging once at the source, then use ctx.logger throughout your pipeline.

Overview

Pipes SDK

Squid SDK

Alternative clients

Basic custom logger

Cloud transports

​Basic custom logger

​Cloud transports

Basic custom logger

Cloud transports