Skip to main content

​
Overview

The Vercel integration enables Steadwing to access deployment logs, build events, and project configurations from your Vercel account. During root cause analysis, Steadwing investigates deployment failures, build errors, and runtime issues to identify the underlying causes of frontend and deployment-related incidents.

​
Why Use Vercel with Steadwing?

Deployment Monitoring

Track deployment status, failures, and build errors in real-time

Build Log Analysis

Analyze complete build logs to identify compilation and dependency issues

Runtime Insights

Monitor runtime logs and errors from deployed applications

Configuration Review

Inspect project settings, environment variables, and Edge Config

​
Setup Instructions

​
Step 1: Create Vercel API Token

  1. Log in to your Vercel account at vercel.com
  2. Navigate to Settings → Tokens
  3. Click Create Token
  4. Configure the token:
    • Token Name: Steadwing Integration
    • Scope: Select the team/account you want to monitor
    • Expiration: Choose an appropriate expiration period (or no expiration)
  5. Click Create Token
  6. Copy the generated token immediately
Save your token immediately! Vercel only shows it once. If you lose it, you’ll need to create a new token.

​
Step 2: Connect Vercel in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the Vercel integration card
  3. Click to expand the collapsible form
  4. Paste your API token in the api_key field
    • The field should show: ••••••••••••••••••••••••••
  5. Toggle the switch to Enable the integration

​
Step 3: Verify Connection

  1. Return to Steadwing Settings
  2. Confirm the Vercel integration shows as Connected
  3. Create a test incident to verify deployment data is being pulled correctly

​
How Vercel Integration Works

​
Data Collection

Steadwing can query Vercel for:
  • Deployments - All deployments across your projects with status and timing
  • Build Logs - Complete build output including errors and warnings
  • Runtime Logs - Application logs from deployed functions and pages
  • Deployment Events - Lifecycle events (queued, building, ready, error, canceled)
  • Deployment Checks - Automated checks and their pass/fail status
  • Project Information - Project configurations, settings, and metadata
  • Edge Config - Feature flags and configuration values
  • Domain Aliases - Custom domains and routing configuration

​
Root Cause Analysis

When analyzing a deployment-related incident, Steadwing:
  1. Identifies deployments around the incident time window
  2. Retrieves build logs for failed or problematic deployments
  3. Analyzes error messages and build failures
  4. Checks deployment events to understand the lifecycle
  5. Reviews deployment checks for quality gate failures
  6. Inspects project configuration for misconfigurations
  7. Examines Edge Config for feature flag issues
  8. Provides deployment-specific insights in the RCA report

​
Available Capabilities

​
Deployment Analysis

  • List all deployments with filtering by project, status, and time
  • Get detailed deployment information including build configuration
  • Retrieve complete build logs with error highlighting
  • Track deployment events and state transitions
  • Review automated deployment checks and results

​
Project Management

  • List all projects in your Vercel account
  • Get project configuration and settings
  • Review environment variables (names only, not values)
  • Inspect build and output settings

​
Edge Configuration

  • List Edge Configs for feature flags and dynamic configuration
  • Get specific Edge Config items and their values
  • Review Edge Config tokens and access controls

​
Team & Access

  • List teams and their members
  • Review authentication tokens (metadata only)
  • Check domain aliases and routing

​
Configuration

​
Required Permissions

The Vercel API token requires:
  • Read access to deployments and build logs
  • Read access to project configurations
  • Read access to Edge Config (if used)
Steadwing does NOT have permission to:
  • Create or modify deployments
  • Change project settings
  • Delete resources
  • Access environment variable values (only names)
  • Modify Edge Config values

​
Supported Features

  • Deployment monitoring and status tracking
  • Build log retrieval and analysis
  • Runtime log collection
  • Deployment event tracking
  • Automated check results
  • Project configuration review
  • Edge Config inspection
  • Domain alias management

​
Token Scopes

When creating your token, you can limit access to:
  • Specific teams or personal account
  • Read-only permissions (recommended)
  • Specific projects (via team selection)

​
FAQs

Steadwing reads deployment logs, build outputs, project configurations, and Edge Config. It does NOT access environment variable values, source code, or modify any settings.
Yes, when creating the API token, select a specific team scope. This limits access to only that team’s projects.
No, Steadwing only has read access. It cannot create, modify, or cancel deployments.
When a deployment-related incident occurs, Steadwing queries deployment logs, build errors, and configuration to identify issues like failed builds, missing dependencies, or environment problems.
If your token expires or is revoked, the integration will stop working. Simply create a new token and update it in Steadwing Settings.
No, Steadwing can only see environment variable names, not their values. This protects sensitive credentials and secrets.
Need additional help? Please reach out to us at [email protected]