Railway

​

Connect a Railway project

1. Open your project in Squasher and select Settings in the sidebar, then the Integrations tab.
2. On the Railway card, select Connect, then approve the access in Railway. Give Squasher access to the Railway project that you want to monitor.
3. Back in Squasher, choose the project in Railway project and select Connect project. When Railway grants access to only one project, Squasher chooses it for you.

​

Send data from your service

1. In Railway, open the service and select Variables.
2. Add SQUASHER_API_KEY and SQUASHER_PROJECT_ID.
3. Connect the service with one of these options, then redeploy it.

import { init, installGlobalHandlers } from "@squasher-ai/node";

init({
  apiKey: process.env.SQUASHER_API_KEY!,
  projectId: process.env.SQUASHER_PROJECT_ID!,
  environment: process.env.RAILWAY_ENVIRONMENT_NAME ?? "production",
});

installGlobalHandlers();

OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.squasher.ai
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=x-squasher-key=<your ingest key>
OTEL_SERVICE_NAME=checkout-api
OTEL_RESOURCE_ATTRIBUTES=deployment.environment.name=production

​

What Squasher keeps

​

Verify

1. Throw one test error in the service, or record a span with ERROR status.
2. In Squasher, select Issues in the sidebar. The error is at the top of the list.

​

Limits

• A Railway connection pulls logs and metrics on a schedule, so they arrive a few minutes late. Send errors from inside the service for issues with stack traces.
• RAILWAY_ENVIRONMENT_NAME is a variable that Railway sets. If your Railway environment has another name than production, automatic AI triage does not run on its issues by default.

​

Next steps

Node.js SDK

See every option of the Node.js SDK.

OpenTelemetry

Set up traces, logs, and metrics in any language.