Vercel
Create a Vercel log drain pointed at your Sazabi intake URL to forward deployment logs from serverless functions, edge functions, and static builds.
About
Stream logs from your Vercel serverless functions, edge functions, and static builds into Sazabi by creating a log drain in the Vercel dashboard. This path covers logs only.
Vercel also has a Connect your account path where Sazabi sets up and maintains drains for logs, traces, and Web Analytics for the projects you pick. See Vercel account connection page for that setup.
Vercel Drains require the Pro or Enterprise plan. Hobby and Pro Trial teams cannot create drains. Sazabi does not parse NDJSON on this endpoint — confirm you set the delivery format to JSON when creating the drain.
Prerequisites
- A Vercel team on the Pro or Enterprise plan.
- Your Sazabi intake URL (shown above).
Set up in the dashboard
Open Drains
In your Vercel dashboard, go to Team Settings > Drains and create a new drain.
Choose log type
Choose Logs as the data to deliver. This self-serve path covers logs only — traces and Web Analytics events are available on the connect-your-account path.
Set the endpoint
Paste your Sazabi intake URL (shown above) into the drain's endpoint field.
Set delivery options
- Delivery format: JSON (Sazabi does not parse NDJSON on this endpoint).
- Projects, environments, and log sources: pick the projects, environments, and log sources to send. Sazabi accepts every Vercel log source: Static, Lambda, Edge, Build, External, Firewall, and Redirect.
Save
Save the drain. Vercel begins delivering logs immediately.
Set up with the CLI
You can also register the Vercel log source with the Sazabi CLI (installed and authenticated — see CLI reference).
Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
sazabi log-sources create vercel --mode connectionlessThe command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run sazabi log-sources get <log-source-id> at any time to reprint the endpoint, or sazabi log-sources list to see every log source in the project.
Verify
Push a deployment or hit an application route to generate log activity. Open the Intake page in the Sazabi dashboard and confirm logs from the Vercel source appear. Logs typically appear within a few minutes.
Troubleshooting
Drain option not visible — Drains appear only on Pro and Enterprise plans. Hobby and Pro Trial teams see no Drains section in Team Settings.
Logs arrive malformed — Confirm you selected JSON as the delivery format. Sazabi does not parse NDJSON on this endpoint; NDJSON payloads will not be processed correctly.
No logs after creating the drain — Verify the endpoint URL in the drain settings matches your Sazabi intake URL exactly. Also confirm the drain is set to deliver at least one log source type and at least one environment.
Traces or Web Analytics events are absent — This self-serve path covers logs only. Connect your Vercel account for Sazabi to create traces and Web Analytics drains.