Dash0 Acquires Lumigo to Expand Agentic Observability Across AWS and Serverless

Last updated: March 3, 2026

Send Vercel Logs to Dash0

The Vercel Integration enables you to send logs produced by your projects in Vercel to Dash0.

Set Up

The recommended way to send logs from Vercel to Dash0 is via Dash0's Vercel integration. Alternatively, you can also set up Vercel log drains manually, see section Setting up log drains manually below.

Set Up via the Vercel Integration

  1. To install the integration, go to https://vercel.com/integrations/dash0 and click the "Connect Account" button.

  2. Vercel's integration installation wizard guides you through the process. In the first step, select the Vercel team from which you want to send logs to Dash0. You can also optionally restrict the set of projects for which you want to receive logs in Dash0, or select "All Projects".

  3. Click on "Connect Account" at the bottom of the dialog to proceed.

  4. After selecting the Vercel team, you will be redirected to the Dash0 UI, which will open in a popup. If you are not signed into Dash0, please sign in now.

  5. If you have access to multiple Dash0 organizations, you need to decide to which Dash0 organization the Vercel logs will be sent. Click on the logo of your Dash0 organization in the upper left to open the list of organizations, then select the target organization.

  6. Optionally you can also select to which dataset the Vercel logs will be sent. By default, it will be Dash0's Default dataset.

  7. Click "Connect my Vercel account to ..." to finish the process.

You will be redirected to your Vercel dashboard afterwards.

That's it! Your Dash0 Vercel integration has been set up and you will start receiving logs from Vercel in Dash0.

In your Vercel settings under "Log Drains" you will also see a new log drain named "dash0-integration-log-drain", which Dash0 has set up automatically for you.

Setting Up Log Drains Manually

This setup is a manual alternative to the Vercel integration setup described above. Some of the setup needs to be executed in Vercel, and some in Dash0. Both parts of the setup are necessary.

Settings in Dash0

To configure and use Vercel's Log Drains capability, you must provide the Dash0 endpoint to send data to and the Dash0 Authorization token.

If you are already using Dash0, you can find it in the onboarding section. If you are just looking for this data, you can find it in the manage section of your organization.

Settings in Vercel

The API Endpoint and Authorization token needs to be specified in Vercel's log drain settings, which can be found under:

Team Settings -> Log Drains (in the left sidebar)

  1. You can choose if you want to forward logs for all projects or only specific projects.

  2. Select the sources, such as Static, Edge, Function, Build, Firewall, etc., for which you want to export logs and choose JSON as the delivery format.

  3. Now specify the environments for which you want to forward logs and select the desired sampling rate. Vercel's documentation provides more details about the sampling rate.

  4. Fill in the API Endpoint URL from Dash0's settings to the Endpoint field.

  5. Authorization when sending data to Dash0 is based on a custom header, so enable "Custom Headers."

  6. Copy x-vercel-verify to the Header Key and copy the value after the colon into the Header value field. Now, you can add a second header using the "Add" button.

  7. Specify Authorization as the Header Key and add Bearer as a prefix to your Authorization token starting with auth_. The value field will contain a value of the format: Bearer auth_XXXXXX

  8. You can Test the Log Drain configuration using the Test button and finalize the configuration using the Add Log Drain button.

Further Customizations

Further customizations are possible by adding the following HTTP headers:

  • X-Dash0-Dataset: If you add the X-Dash0-Dataset header to the log drain configuration, the header value will be converted to the resource attribute dash0.dataset and the logs will be routed to the matching dataset in Dash0.

  • X-Dash0-Disable-Open-Telemetry-Semantic-Conventions: If this header is defined with the value 1, no conversion to OpenTelemetry semantic conventions will be performed. Instead, the log attributes will be converted exclusively to attribute names with the prefix vercel.

Log Types

Dash0 supports all log types that Vercel provides:

  • Static: access logs for static assets like HTML and CSS files
  • Edge: log data from edge functions like middleware
  • Function: log data from Vercel functions like API routes
  • External: log results for external rewrites to a different domain
  • Build: log data from build steps
  • Firewall: log data from requests denied by Vercel Firewall rules

Log Attribute Conversion

Attributes on Vercel log records are converted as follows:

Resource Attributes (Default)

Vercel AttributeOpenTelemetry Attribute
projectIdvercel.project_id
deploymentIdvercel.deployment_id
projectNameservice.name
environmentdeployment.environment
branchvercel.branch
buildIdvercel.build_id
sourcevercel.source
executionRegionfaas.invoked_region

Log Record Attributes (Default)

Vercel AttributeOpenTelemetry Attribute
idlog.record.uid
hostserver.address
entrypointvercel.entrypoint
pathhttp.route
requestIdfaas.invocation_id
statusCodehttp.response.status_code
destinationvercel.destination
typelog.iostream (if value is stdout or stderr), otherwise vercel.type
proxy.timestampvercel.proxy.timestamp
proxy.methodhttp.request.method
proxy.schemeurl.scheme
proxy.hosturl.domain
proxy.pathurl.path
proxy.userAgentuser_agent.original
proxy.referervercel.proxy.referer
proxy.statusCodehttp.response.status_code
proxy.clientIpnetwork.peer.address
proxy.regioncloud.region
proxy.cacheIdvercel.proxy.cache_id
proxy.vercelCachevercel.proxy.cache_value
proxy.pathTypevercel.proxy.path_type
proxy.vercelIdvercel.proxy.vercel_id

Resource Attributes (With X-Dash0-Disable-Open-Telemetry-Semantic-Conventions=1)

Vercel AttributeMapped Attribute
projectIdvercel.project_id
deploymentIdvercel.deployment_id
projectNamevercel.project_name
environmentvercel.environment
branchvercel.branch
buildIdvercel.build_id
sourcevercel.source
executionRegionfaas.invoked_region

Log Record Attributes (With X-Dash0-Disable-Open-Telemetry-Semantic-Conventions=1)

Vercel AttributeMapped Attribute
idvercel.log_id
hostvercel.host
entrypointvercel.entrypoint
pathvercel.path
requestIdvercel.request_id
statusCodevercel.status_code
destinationvercel.destination
typevercel.type
proxy.timestampvercel.proxy.timestamp
proxy.methodvercel.proxy.method
proxy.schemevercel.proxy.scheme
proxy.hostvercel.proxy.host
proxy.pathvercel.proxy.path
proxy.userAgentvercel.proxy.user_agent
proxy.referervercel.proxy.referer
proxy.statusCodevercel.proxy.status_code
proxy.clientIpvercel.proxy.client_ip
proxy.regionvercel.proxy.region
proxy.cacheIdvercel.proxy.cache_id
proxy.vercelCachevercel.proxy.cache_value
proxy.pathTypevercel.proxy.path_type
proxy.vercelIdvercel.proxy.vercel_id