Vercel supports automatic log and OpenTelemetry (OTel) trace export to SigNoz without code changes using log and OpenTelemetry drains.
Want a one-click setup? Install the SigNoz integration from the Vercel Marketplace — it creates the drains for you automatically.
Prerequisites
- A Vercel Pro or Enterprise account
- An instance of SigNoz Cloud
Configure Vercel Drains
Create a separate drain for each signal you want to export:
Step 1: Create a New Log Drain
- Navigate to Team Settings > Drains and click Add Drain. This opens a dialog to configure your new drain.
- Select Logs as the drain type.
- Provide a name for your drain, select which projects should send data to your endpoint, and configure the log source and environment.
- Click Next.
Step 2: Configure the Log Destination
- Under the Custom Endpoint tab, set the delivery format to
JSON. - Enter the SigNoz logs ingestion endpoint:
https://ingest.<region>.signoz.cloud:443/logs/json
Replace <region> with your SigNoz Cloud region.
- Enable Custom Headers and add the following header:
signoz-ingestion-key: <your-ingestion-key>
Replace <your-ingestion-key> with the ingestion key from your SigNoz Cloud account. You can find this under Settings > Ingestion Settings in SigNoz.
Step 3: Test and Create the Log Drain
Click Test to ensure your endpoint receives the data correctly. If the test is successful, click Create Drain.
Your Vercel logs will now be streamed to SigNoz Cloud.
It might take some time for the data to appear.
Validate
After creating the drain, verify that the data is flowing into SigNoz:
- Open Logs Explorer in your SigNoz Cloud dashboard.
- Wait a few minutes for logs to arrive — there may be a short delay.
- Look for log entries with Vercel-specific attributes such as
source,projectName, anddeploymentId. - If you see log entries from your Vercel projects, the integration is working correctly.
Step 1: Create a New Trace Drain
- Navigate to Team Settings > Drains and click Add Drain. This opens a dialog to configure your new drain.
- Select Traces as the drain type.
- Provide a name for your drain, select which projects should send data to your endpoint, and configure the sampling rate.
- Click Next.
Step 2: Configure the Trace Destination
- Under the Custom Endpoint tab, set the delivery format to
JSONorProtobuf(Protobuf is recommended for performance). - Enter the SigNoz OTLP HTTP traces ingestion endpoint:
https://ingest.<region>.signoz.cloud:443/v1/traces
Replace <region> with your SigNoz Cloud region.
- Enable Custom Headers and add the following header:
signoz-ingestion-key: <your-ingestion-key>
Replace <your-ingestion-key> with the ingestion key from your SigNoz Cloud account. You can find this under Settings > Ingestion Settings in SigNoz.
Step 3: Test and Create the Trace Drain
Click Test to ensure your endpoint receives the data correctly. If the test is successful, click Create Drain.
Your Vercel traces will now be streamed to SigNoz Cloud.
It might take some time for the data to appear.
Validate
After creating the drain, verify that the data is flowing into SigNoz:
- Open Traces in your SigNoz Cloud dashboard.
- Wait a few minutes for traces to arrive — there may be a short delay.
- Look for trace entries originating from your Vercel projects.
- If you see trace entries from your Vercel applications, the integration is working correctly.
Troubleshooting
No data appearing in SigNoz
- Incorrect region: Verify that
<region>in the endpoint URL matches your SigNoz Cloud region. - Invalid ingestion key: Confirm the
signoz-ingestion-keyheader value matches the key shown in your SigNoz Cloud settings. - Drain not active: Check the drain status in Team Settings > Drains in Vercel. If it shows an error, click the drain to see details.
- Verification: After applying fixes, click Test in your Vercel drain config and check the SigNoz Logs Explorer or Traces again.
Drain creation or test fails
- Endpoint URL format: Ensure the URL matches exactly based on your drain type (
/logs/jsonor/v1/traces) with no trailing slash or extra path segments. - Missing headers: Confirm the
signoz-ingestion-keycustom header is set and the value does not contain leading/trailing whitespace. - Verification: Once corrected, the Test button in Vercel should return a successful response.
Next Steps
- Set up alerts to get notified when your Vercel applications contain errors.
- Create a dashboard to visualize telemetry volume, error rates, and latency across your Vercel projects.
Get Help
If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack.
If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.