Skip to main content
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).
Estimated time: 5 minutes. Incidents need only a webhook; agent tools also need a Better Stack API token.

Prerequisites

  • A Better Stack account with Uptime and/or Telemetry
  • For agent tools: an API token with access to the resources you want Clarion to read

Connect

  1. In Clarion, open Integrations, find Better Stack, and add a monitor. Adding it connects Better Stack.
  2. Copy the monitor’s webhook URL and X-Webhook-Secret value. The secret is shown once; you can rotate it from the monitor later.
  3. In Better Stack, add a webhook that posts incidents to that URL, with a custom X-Webhook-Secret header set to the secret.
  4. Optional, for agent tools: create a Better Stack API token, then paste it at setup’s Add an API token step, or later under Configuration on the Better Stack integration page. It also adds each incident’s details and comments to its issue.

What Clarion ingests

Uptime incidents and alerts feed the Infrastructure & Ops 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.
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.

Disconnect

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