> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bronto.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Vercel Build and Deployment Logs

> Send Vercel build logs to Bronto with the log drain, and deployment events (created, succeeded, failed, canceled, promoted) with commit and branch through webhooks.

Every build writes its output to the log drain (`source = 'build'`), tagged with the deployment ID and the environment (`production` or `preview`). The deployment's state changes and the commit it came from aren't in any drain; they come through webhooks.

## Recommended method

[**Marketplace connector**](/integrations/vercel-connector.md): its log drain carries build logs for production and preview deployments.

## Alternatives

* [**Deployment webhooks**](/integrations/vercel-webhooks.md): one event per state change (`deployment.created`, `.succeeded`, `.error`, `.canceled`, `.promoted`) with commit SHA, message, author and branch, as deploy markers in Bronto.

## Worth knowing

In testing, a failed build logged its errors at `level: info` with `type: stderr`, not at `level: error`. To find failed builds in the log drain, search the text:

```
source = 'build'
  AND (@raw ILIKE '%Build error occurred%'
    OR @raw ILIKE '%exited with 1%')
```

The `deployment.error` webhook event reports failures directly.

See [Ingesting Vercel Data into Bronto](/integrations/vercel.md) for the full mapping.

## References

* [Vercel builds](https://vercel.com/docs/builds)
* [Vercel webhooks](https://vercel.com/docs/webhooks)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.