Vercel telemetry

Use the Vercel integration when you want zero-code capture for deployment and runtime errors.

One-click setup

In Squasher, open Settings > Integrations > Vercel and select Connect.
Approve the Vercel integration and select a Vercel project.
Squasher validates the endpoints and creates project-scoped log and trace drains.
Run the opt-in verification and confirm that the selected project sends a test signal.

Squasher also creates a restricted ingest key for the drains. It stores the owned Vercel drain IDs, so a project change or disconnect removes the old drains and revokes the old key. Squasher does not enable drains for every project in your Vercel account.

Vercel Drains require a Pro or Enterprise plan. The Vercel installation must grant the log-drain read and write permission. Reconnect the integration if this permission was added after install.

The Squasher Vercel integration must be installed for the selected account or team. Vercel requires integration registration before customers can install it. See Vercel’s integration permissions and Drains documentation. You can self-serve this integration with the public API, the CLI, or the Squasher MCP server without opening the dashboard first. Connected Vercel deployment webhooks also create first-class deployment records. Squasher matches those records to SDK telemetry when service.name and service.version line up with the deployment metadata or commit SHA.

Verified against Vercel’s current drains documentation: log drains send HTTPS batches, support custom endpoints, and let you control sources and environments from the Vercel dashboard.

Manual setup

Use this fallback when you do not want to grant Squasher permission to manage Vercel drains.

API, CLI, or MCP onboarding

squasher log-connectors onboard --project <project-id> --connector-key vercel --display-name "Vercel production"

{
  "mcp": "search(\"logConnectors.onboard\"), then execute the generated request",
  "body": {
    "connector_key": "vercel",
    "display_name": "Vercel production",
    "config": {}
  }
}

curl -X POST "https://api.squasher.ai/v1/projects/<project-id>/log-connectors/onboard" \
  -H "x-squasher-key: <api-key>" \
  -H "Content-Type: application/json" \
  -d '{"connector_key":"vercel","display_name":"Vercel production","config":{}}'

Each option returns the exact drain URL and snippet to paste into Vercel.

Get your drain URL

Use the Squasher project-specific Vercel drain endpoint from your dashboard settings.

Add the drain in Vercel

Configure a custom log drain in your Vercel project and point it at the Squasher endpoint.

Verify delivery

Trigger an application or deployment error and confirm Squasher creates an issue in the dashboard.

What Squasher uses

Squasher ingests Vercel log entries for context, then creates error groups from high-severity or failed-request events.

When to combine it with an SDK

Use the Next.js SDK together with the drain if you want richer application context like breadcrumbs, user data, and precise stack frames.

Get Started

SDKs

Integrations

Migrations

Cloud Log Drains

Features

API Reference

One-click setup

Manual setup

API, CLI, or MCP onboarding

What Squasher uses

When to combine it with an SDK

​One-click setup

​Manual setup

​API, CLI, or MCP onboarding

​What Squasher uses

​When to combine it with an SDK

One-click setup

Manual setup

API, CLI, or MCP onboarding

What Squasher uses

When to combine it with an SDK