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

# Better Stack

> Uptime monitoring, incident alerts, and telemetry queries — connect Better Stack so agents can investigate and act on outages.

Better Stack brings uptime incidents into Clarion and gives agents a wide tool surface over both **Uptime** (incidents, monitors, heartbeats, on-call, status pages) and **Telemetry** (log and metric queries, dashboards).

<Note>
  **Estimated time:** 3 minutes. You will need a Better Stack **API token**.
</Note>

## Prerequisites

* A **Better Stack** account with Uptime and/or Telemetry
* An API token with access to the resources you want Clarion to read

## Connect

1. In Better Stack, create an **API token**.
2. In Clarion, open **Integrations** and find **Better Stack**.
3. Paste the **API Token** and click **Connect**.

## What Clarion ingests

Uptime incidents and alerts feed the [Infrastructure & Ops](/learn/agents/our-agents) agent's outage runbook.

## What agents can do

Better Stack has one of the broadest tool surfaces in Clarion. The highlights:

**Incidents** — list and read incidents, read the incident timeline and comments, add a comment, acknowledge, resolve, create, and escalate an incident; read escalation options, policies, and severities.

**Monitoring** — list and read monitors, heartbeats, and their availability and response-time history.

**On-call** — read the current on-call, on-call events, and rotations.

**Status pages** — list and read status pages and their resources, and publish a status-page report and updates.

**Telemetry** — run log and metric queries, build explore and metric queries, read sources and their fields, inspect errors and update their state, list releases and applications, and create or edit dashboards and charts.

<Warning>
  Several of these write to Better Stack — resolving an incident, publishing a status-page update, creating a dashboard. They are gated by your workspace's tool policy and ask for approval unless explicitly allowed.
</Warning>

## Disconnect

Click **Disconnect** on the integration page. The stored token is deleted and the tools disappear from agent skills.