> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Better Stack

> Connect Better Stack for uptime monitors, incidents, and telemetry.

Better Stack uses **two separate API tokens** — one for Uptime, one for Telemetry
— and you provide whichever you use (at least one). With them the agent can work
with your uptime monitors, incidents, and telemetry.

## Connect

### Create your tokens

* **Uptime API token** — from Better Stack's Uptime API settings.
* **Telemetry API token** — from Better Stack's Telemetry API settings.

### Connect in Nuphos

In **Connectors → Connect → Better Stack**, enter:

| Field                   | Notes                                           |
| ----------------------- | ----------------------------------------------- |
| **Label**               | A friendly name, e.g. "Production Better Stack" |
| **Uptime API Token**    | Optional — for monitors, heartbeats, incidents  |
| **Telemetry API Token** | Optional — for dashboards, sources, metrics     |

At least one token is required. Each token you provide is verified against the
Better Stack API before saving.

### Optional extras

* **Dashboard team ID** — lets Nuphos deep-link into your Better Stack dashboards.
* **Prometheus webhook URL** — point Better Stack's Alertmanager-style webhook at
  Nuphos so alerts flow in.

## In the Nuphos app

Your monitors, heartbeats, and incidents feed the unified
[Monitoring overview](/observability/monitoring) — one place to see uptime and
liveness across all your observability providers, with deep links back into
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 dashboards, sources, and metrics. In practice:

* *"Anything down right now?"* — it reads monitors and active incidents and
  summarizes.
* *"Set up an uptime monitor for the new API endpoint"* — a change, so it
  proposes a [plan](/agent/plans) and creates the monitor once you approve.
* *"Why did the heartbeat for the nightly job miss?"* — it combines Better Stack
  signals with what it can see through your other
  [connectors](/connectors/overview) to find the cause.

## Permissions & authorization

Two boundaries govern what happens through this connector:

* **Hard boundary — who can use it.** Only team **Administrators** can bind or
  remove the tokens, and they can restrict the binding to specific members with
  a [member allow-list](/security/access-control). Within a session the agent
  only holds credentials you explicitly selected, re-checked on every request.
* **Soft boundary — what the agent may do with it.** Reading monitors,
  incidents, and telemetry is free-form; creating or changing monitors goes
  through [plan approvals](/security/approvals) and
  [Auto-authorization](/security/auto-mode).

The outer limit is which tokens you provided: give only the Uptime token and the
agent can't touch Telemetry at all, and vice versa.

## Good to know

* The two tokens are independent — you can start with one product and add the
  other later by updating the binding.
* With the **Prometheus webhook** configured, Better Stack alerts flow into
  Nuphos as they fire rather than waiting to be polled.