Vercel

Firetiger ingests data from Vercel via Vercel Drains (also referred to as Log Drains or Log Sinks). Two drains are involved: one sends logs to Firetiger over HTTP, and one sends OTLP traces. Together they cover the same surface as the one-click setup on the Firetiger Integrations page — this guide documents the manual equivalent so you can configure it by hand if the auto-setup fails or your organization restricts personal access tokens.

Prerequisites

  • An owner or admin role on the Vercel team that owns the projects you want to send data from.
  • Your Firetiger ingest credentials. The endpoint, username, and password are visible on the Integrations page in the Firetiger console.

  • A Base64-encoded username:password pair for the Authorization header:

    echo -n "username:password" | base64

    Replace username and password with the values from the Integrations page. Save the output — you will paste it into both drains below.

Configure the logs drain

  1. Open the Vercel dashboard and navigate to your team’s settings.

  2. Go to Drains > Create Drain.

  3. Configure the drain:
    • Name: Send logs to Firetiger
    • Projects: select the projects to send logs from.
    • Schema: Log (version v1)
    • Delivery type: HTTP

    • Endpoint:

      https://ingest.cloud.firetiger.com/vercel/logs
    • Encoding: JSON
    • Custom headers: add a header named Authorization with value Basic <base64-credentials>, where <base64-credentials> is the output from the Base64 command above.
  4. Configure the filter:
    • Sources: Lambda and Edge (the auto-setup uses these two; add Build and Static if you also want to ingest build and static-asset logs).
    • Environments: Production. Add Preview if you want preview deployments to flow into Firetiger as well.
  5. Save and enable the drain.

Configure the traces drain

Vercel sends traces as OTLP over HTTP. Create a second drain alongside the logs drain.

  1. From the same Drains page, click Create Drain again.

  2. Configure the drain:
    • Name: Send traces to Firetiger
    • Projects: select the same projects you chose for the logs drain.
    • Schema: Trace (version v1)
    • Delivery type: OTLP HTTP

    • Endpoint:

      https://ingest.cloud.firetiger.com/v1/traces
    • Encoding: JSON
    • Custom headers: add the same Authorization: Basic <base64-credentials> header you used for the logs drain.
  3. Save and enable the drain.

Verifying ingest

Trigger a deployment or fresh request against one of the selected projects, then:

  • Open the Integrations page in the Firetiger console and check the Detected sources panel — Vercel logs should appear within a minute.
  • Logs land in the vercel_logs table; traces are merged into your OpenTelemetry traces table.
  • If a drain reports delivery errors in the Vercel dashboard, double-check the endpoint URL and the Base64 of your ingest credentials. Firetiger’s ingest endpoint always returns 200 OK on a successful POST so Vercel will not auto-disable the drain on transient errors.
This site uses Just the Docs, a documentation theme for Jekyll.