Vercel

Forward logs from Vercel deployments to Sazabi for AI-powered analysis and investigation.

Vercel is a native data source. Sazabi creates log drains for your Vercel projects to forward logs automatically.

About this data source

When you connect your Vercel account, Sazabi provisions log drains on your selected projects. These drains stream log events to Sazabi's intake in real-time, giving you:

Automatic log forwarding without managing infrastructure
Real-time streaming of build, runtime, and edge logs
Selective forwarding from specific projects
AI-powered analysis and investigation of your deployment logs

Prerequisites

Before you begin, make sure you have:

A Vercel account with Pro or Enterprise plan (log drains require a paid plan)
A Vercel API token with read and write permissions
Projects you want to forward logs from

Log drains are only available on Vercel Pro and Enterprise plans. If you are on the Hobby plan, you will need to upgrade before setting up this integration.

Setup

Create a Vercel API token

Generate an API token in your Vercel account settings:

Go to Vercel Account Settings > Tokens
Click Create Token
Give it a descriptive name like "Sazabi Log Forwarding"
Set the scope to Full Account or the specific team you want to connect
Copy the token and store it securely

The token needs read and write permissions to create log drains on your projects.

Data Sources

Select Vercel from the list of available data sources.

Enter your Vercel API token when prompted.

Specify team (optional)

If you are connecting a Vercel team (rather than a personal account), enter your team ID or slug. You can find this in your team settings URL:

https://vercel.com/teams/YOUR_TEAM_SLUG/settings

Leave this empty if you are connecting a personal Vercel account.

Select projects

After authenticating, Sazabi displays a list of your Vercel projects. Select the projects you want to forward logs from.

You can select individual projects or all projects in your account/team.

Confirm and connect

Review your selections and click Connect. Sazabi will create log drains on each selected project. Logs will begin flowing within a few minutes.

What Sazabi creates

When you connect Vercel, Sazabi provisions the following resources:

Log drain on each selected project, configured to forward logs via JSON over HTTPS

Log drains are visible in your Vercel project settings under Settings > Log Drains.

Log types

Vercel log drains forward the following log types:

Build logs: Output from your build process
Runtime logs: console.log and other output from your serverless functions
Edge logs: Logs from edge functions and middleware
Static logs: Access logs for static files (if enabled)

All log types are automatically tagged in Sazabi, allowing you to filter and search by log type.

Verifying logs are flowing

Once connected, you can verify that logs are flowing to Sazabi:

Ask the assistant: Open a thread in Sazabi and ask "Show me recent Vercel logs" or "What errors appeared in my deployments today?"
Check the dashboard: Navigate to your project in the Sazabi dashboard to see logs appear in real-time.
Deploy something: Push a change to your repository or trigger a manual deployment, then verify the build and runtime logs appear in Sazabi.

Disconnecting

When you disconnect Vercel from Sazabi:

Sazabi removes all log drains it created on your projects
No logs are deleted from Vercel
Historical logs already sent to Sazabi remain available until retention expires

To disconnect, go to Settings > Data Sources, find your Vercel connection, and click Disconnect.

If the connection fails, verify your API token has the correct scope. The token needs read access to list projects and write access to create log drains. Generate a new token with Full Account scope if needed.

Pro plan required

Log drains are only available on Vercel Pro and Enterprise plans. If you see an error about log drains not being available, check your plan in Vercel account settings.

Log drain already exists

Each project can have a limited number of log drains. If Sazabi cannot create a drain, check if you have existing drains in the project settings and remove any that are no longer needed.

Team ID not found

If you are connecting a team and see a "team not found" error, verify you are using the correct team ID or slug. The team slug is visible in your team settings URL. Also confirm your API token has access to the team.

Logs not arriving

Verify the log drain was created in your Vercel project settings
Trigger a new deployment to generate fresh logs
Check that your Sazabi API key is valid and the project is active
Allow a few minutes for logs to propagate through the pipeline