Skip to main content

​
Overview

The Better Stack integration enables Steadwing to pull uptime monitoring, incident management, and on-call data from your Better Stack account. During root cause analysis, Steadwing gathers monitor states, incident timelines, heartbeat status, and on-call schedules to correlate signals across your entire stack and identify root causes faster.

​
Why Use Better Stack with Steadwing?

Incident Context

Pull active and recent incidents, their timelines, cause, and resolution status automatically

Uptime Monitoring

Check which monitors are up or down, response times, and affected regions

Heartbeat Tracking

Verify whether cron jobs, background workers, and scheduled tasks are still reporting in

On-Call Visibility

See who was on-call when the incident happened and escalation policy details

​
Setup Instructions

​
Step 1: Create a Better Stack API Token

  1. Log in to your Better Stack account
  2. Navigate to Settings → API tokens
  3. Click Create API token
  4. Configure the token:
    • Name: Steadwing Integration
    • Permissions: Read-only
  5. Click Create
  6. Copy the generated API token
Use a read-only token for security — Steadwing only reads data, it never creates or modifies anything in your Better Stack account.

​
Step 2: Connect Better Stack in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the Better Stack integration card
  3. Click to expand the collapsible form
  4. Paste your API token in the API Token field
  5. Toggle the switch to Enable the integration

​
How Better Stack Integration Works

​
Data Collection

Steadwing queries Better Stack for:
  • Incidents - Active and recent incidents, their timelines, cause, and resolution status
  • Monitor States - Which monitors are up/down, response times, and regions affected
  • Heartbeat Status - Whether expected cron jobs, background workers, or scheduled tasks are still reporting in
  • On-Call Schedules - Who was on-call when the incident happened and escalation policy details
  • Status Page Data - Current status page reports and any ongoing maintenance windows
  • Webhook & Integration Info - How alerts are being routed to other tools (Slack, PagerDuty, etc.)

​
Configuration

​
Required Permissions

The Better Stack API token requires read access to:
  • Incidents - Read incident data, timelines, and updates
  • Monitors - Read monitor status, response times, and availability
  • Heartbeats - Read heartbeat status and check-in history
  • On-Call - Read on-call calendars, schedules, and escalation policies
  • Status Pages - Read status page reports and maintenance windows
  • Metadata - Read severity levels, monitor groups, and webhook integrations
Using a read-only API token is recommended. Steadwing only needs to read monitoring and incident data and never modifies your Better Stack configuration.

​
FAQs

Steadwing only requires a read-only API token. It never writes, updates, or deletes any data in your Better Stack account.
No. Better Stack uses API token authentication — just paste your token in Steadwing Settings and the integration connects immediately. No OAuth redirect required.
No. Steadwing only has read access. It queries monitor states, incidents, and on-call data but never modifies configurations or data.
On-call data helps the RCA agent understand who was responsible during the incident and how escalation policies were applied, providing context for the incident timeline.
The integration will stop working. Simply create a new API token in Better Stack and update it in Steadwing Settings to reconnect.
Need additional help? Please reach out to us at hello@steadwing.com