> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Vercel

> This topic explains how to send logs from Vercel to LaunchDarkly's observability features.

> For the complete documentation index, see [llms.txt](/llms.txt). For the full documentation snapshot, see [llms-full.txt](/llms-full.txt).

## Overview

This topic explains how to send logs from Vercel to LaunchDarkly's observability features.

If you deploy your applications on Vercel, you can configure a log drain to automatically forward your server-side logs to LaunchDarkly. This includes build logs, serverless function logs, edge function logs, and static access logs. Once configured, these logs appear in the [Logs](/home/observability/logs) page of the LaunchDarkly user interface.

## Prerequisites

Before you configure the Vercel log drain, you must:

* Have a Vercel account with at least one project
* Have LaunchDarkly observability enabled for your project
* Know your LaunchDarkly client-side IDTo find your client-side ID:

1. In the LaunchDarkly UI, click the project dropdown to open the project menu.
2. Select **Project settings**.
3. Click **Environments**.
4. Find the environment you want to use and copy the **Client-side ID** value.

## Configure the Vercel log drain

You can configure the log drain directly in the Vercel dashboard.

To configure the Vercel log drain:

1. In Vercel, navigate to your team or account **Settings**.
2. Click **Log Drains** in the sidebar.
3. Click **Add Log Drain**.
4. Select the **Projects** and **Environments** you want to collect logs from.
5. Select **Sources** to specify which types of logs to send. You can choose from:
   * **Build** logs
   * **Edge** function logs
   * **Lambda** (serverless function) logs
   * **Static** access logs
6. For **Delivery format**, select **NDJSON**.
7. For **Endpoint**, enter `https://pub.observability.app.launchdarkly.com/vercel/v1/logs`.
8. Click **Add Custom Headers**.
9. Add a header with the name `x-highlight-project` and set the value to your LaunchDarkly client-side ID.
10. Click **Verify** to test the connection.
11. Click **Create Log Drain** to save the configuration.

## Verify that logs are being received

After you configure the log drain, Vercel begins forwarding logs to LaunchDarkly.

To verify that your logs are being received:

1. In the LaunchDarkly UI, expand **Observe** in the left navigation.
2. Click **Logs**.
3. Look for logs with `source:vercel` or from your Vercel-deployed services.

It may take a few minutes for logs to appear after you first configure the log drain.

## Search attributes

Logs from Vercel include the following attributes that you can use when searching:

\| Attribute

| Description |
| - |

\| --- |
\| `vercel.source`

\| The source of the log, such as `lambda` , `edge` , `build` , or `static` . |
\| `vercel.projectId`

\| The Vercel project ID. |
\| `vercel.deploymentId`

\| The Vercel deployment ID. |
\| `vercel.host`

\| The hostname that served the request. |
\| `vercel.path`

\| The request path. |
\| `vercel.statusCode`

\| The HTTP status code of the response. |

To learn more about searching for logs, read [Search specification](/home/observability/search).

## Filtering logs

You can configure ingestion filters to control which logs from Vercel are stored in LaunchDarkly. This is useful for excluding noisy logs or limiting ingestion to stay within your observability quotas.

To learn more, read [Filters](/home/observability/settings#filters).