Skip to main content
A Vercel drain sends the logs of your Vercel projects to Squasher. Log lines at error or fatal level become issues, and all other lines stay searchable as logs.

Prerequisites

  • A Vercel team on the Pro or Enterprise plan. Vercel offers drains on these plans only.
  • An ingest key and the project ID. See Create an ingest key.

Connect Vercel from Squasher

Squasher can create and manage the drains for one Vercel project:
  1. Open your project in Squasher and select Settings in the sidebar, then the Integrations tab.
  2. On the Vercel card, select Connect, then install the Squasher integration in Vercel.
  3. Back in Squasher, choose the Vercel project in Vercel project and select Connect project. When the integration can see only one Vercel project, Squasher chooses it for you.
Squasher then creates a logs drain and a traces drain for that project. To stop, select Disconnect on the Vercel card: Squasher removes the drains that it created.

Set up the drain by hand

  1. In Vercel, open Team Settings and select Drains.
  2. Select Add Drain, then choose Logs.
  3. Choose the projects, log sources, and environments to send.
  4. Choose Custom Endpoint and set Endpoint URL to https://ingest.squasher.ai/v1/drain/vercel/<project-id>.
  5. Set Format to NDJSON or JSON.
  6. In Custom Headers, add one line: x-squasher-key: <your ingest key>.
  7. Leave Signature Verification Secret empty, then select Create Drain.

What Squasher keeps from each record

Squasher does not read statusCode. A request that returns 500 without an error-level log line does not create an issue.

Verify

  1. Select Test on the drain in Vercel. Squasher answers 200 when the URL and key are correct, and 401 or 403 when they are not.
  2. Deploy a route that calls console.error("Squasher test error"), and open it once.
  3. In Squasher, select Issues in the sidebar. The test error is at the top of the list.
If nothing arrives, check that the key in Custom Headers is complete and that the project ID in the URL belongs to that key.

Limits

  • Squasher drops the Vercel environment field, so issues from the drain have no environment. Automatic AI triage does not run on them. Select Run triage in the Squasher triage card on the issue.
  • Squasher does not check the x-vercel-signature header. The ingest key protects the endpoint.
  • The drain carries logs only. For traces, instrument your app with OpenTelemetry.
For stack traces and request context, use the drain together with the Next.js SDK. The drain adds build and platform logs that the SDK does not see.

Next steps

Next.js SDK

Capture server errors with stack traces.

Drain record format

See how Squasher reads every drain record.

Read AI triage

Learn what the triage summary tells you.

Set up notifications

Send new issues to Slack, PagerDuty, or email.