Vercel Build and Deployment Logs - Bronto Docs

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: its log drain carries build logs for production and preview deployments.

Alternatives

Deployment webhooks: 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 for the full mapping.

References