Better Stack integration: connect Better Stack to Polylane
Connect Better Stack uptime monitors, incidents and telemetry sources to Polylane. Route incident webhooks into investigations with their uptime evidence.
Get started for freeWhat Polylane does with Better Stack.
Incidents triaged on arrival
Every Better Stack incident lands in Polylane as an alert, and an agent triages it the moment it does, correlated with recent changes across the graph.
Uptime mid-investigation
Agents check monitor status, availability, response times, and heartbeats while they work an incident, and every finding is cited back to the monitor behind it.
Availability becomes checks
Monitors, incident volume, and probe latency run as checks on a cadence; agents flag results that stray from the service's normal.
First-class in the graph
Better Stack joins the context graph as a source, so a failing monitor lands next to the deploy and the resources behind it.
How to set up Better Stack
- Create a Global API token in Better Stack Settings → Global API tokens.
- On the same page, use Team-based tokens for the Uptime token. Create the Telemetry token under Telemetry → Settings → API tokens.
- Paste all three tokens into Polylane, validate and connect. The credentials cover different product APIs rather than substituting one token for all three.
Permissions and access
The connection requires Global, Uptime and Telemetry API credentials. Polylane encrypts them before storing them. Alert provisioning writes an outgoing webhook named polylane; the checked form does not enumerate granular provider permissions for each credential, so review the token capabilities in Better Stack.
Discovery, refresh and the connected view
Agents read uptime monitors, up/down status, availability, response times, incidents and their timelines. Heartbeats, status pages and telemetry sources provide additional investigation context. The outgoing webhook covers every incident, including incidents from monitors created later; there is no per-monitor webhook attachment to maintain.
Example workflow
Investigate a failed heartbeat alongside the corresponding uptime incident timeline and telemetry source. The incident webhook brings the outage to Polylane, and the investigation can read Better Stack’s status and response evidence before looking at the connected infrastructure.
Disconnect and revoke access
Disconnect Better Stack in Polylane and revoke all three API tokens in Better Stack. Terraform-managed monitors need no extra webhook field: alert delivery lives on the outgoing webhook managed by the integration.
Tools for the investigation.
What Polylane can do with Better Stack while it investigates. Every call is recorded in the transcript.
betterstackApi Call any Better Stack REST endpoint that lacks a dedicated tool
betterstackMonitors Read or create Better Stack uptime monitors
betterstackIncidents Read Better Stack incidents and their timelines, or acknowledge/resolve one
betterstackHeartbeats List Better Stack heartbeats (cron/job check-ins)
betterstackStatusPages List Better Stack status pages
betterstackStatusReports Read and publish Better Stack status page reports (public incident communication)
betterstackSources List Better Stack telemetry sources
Common questions.
Can I connect Better Stack with only an Uptime token?
The connection form asks for three product credentials: Global, Uptime and Telemetry. They cover different API surfaces.
Do new Better Stack monitors need a Polylane webhook?
No per-monitor configuration is required. The outgoing webhook covers every incident, including those from new monitors.