Pangea Docs FAQ Get early access

Docs / Observability and data

Better Stack

Connect Better Stack Uptime and Telemetry so the agent can work with monitors, incidents, sources and metrics.

Better Stack uses two separate API tokens, one for Uptime and one for Telemetry. Provide the one you use, or both. With them the agent can work with your uptime monitors, heartbeats, incidents and telemetry.

Connect

1. Create your tokens

2. Connect in Pangea

As a team Administrator, open Connectors → Connect → Better Stack and fill in:

Field Notes
Label A friendly name, for example Production Better Stack
Uptime API Token Optional. Enables Uptime monitors and monitor management
Telemetry API Token Optional. Enables Telemetry sources, collectors, dashboards and metrics

You need at least one token. Pangea checks each token against the Better Stack API before it saves the connection, then stores it encrypted.

In the Pangea app

A connected account gets its own pages: Monitors, Incidents, Sources and Dashboards. Pages that need a missing token tell you which token to add.

Your monitors, heartbeats and incidents also feed the Monitoring overview, with links back to Better Stack for the full detail.

What the agent can do for you

The agent can list and manage Uptime monitors, heartbeats and incidents, and read Telemetry sources, dashboards and metrics. For example:

Start agent work from a Better Stack incident

To have an incident start agent work, create an outgoing webhook in Better Stack that points to a Pangea webhook trigger. Check its scope and delivery settings, and confirm a test delivery arrives before you rely on it.

Permissions

Team Administrators connect and remove this connection. They can limit who uses it with a member allow-list. Better Stack's token permissions stay the outer limit.

Individual actions follow Auto Mode and Full Access. Significant infrastructure work goes through plans.

Good to know