Better Stack
Connect
Connect Better Stack from the terminal. Pass --help for the flags Better Stack accepts.
praxen integration connect --type betterstackGlobal, Uptime, and Telemetry API tokens.
Connect Better Stack so agents can check uptime monitors, investigate incidents, and inspect telemetry sources.
Setup
Better Stack scopes API tokens per product, so the connect flow asks for three:
- Global API token: betterstack.com/settings/global-api-tokens.
- Uptime API token: same page, under the Team-based tokens tab.
- Telemetry API token: Telemetry → Settings → API tokens.
- Paste each token into Praxen Inc. Praxen Inc. validates them and connects.
Your tokens are encrypted before they are stored, and the agent never sees them.
Praxen Inc. provisions an outgoing webhook named praxen in Better Stack so incidents land as alerts and get triaged as they fire. The webhook covers every incident, so monitors need no per-monitor setup: ones you create later are covered automatically.
What agents can do
- List monitors and check up/down status, availability, and response times
- Investigate incidents and their timelines
- Check heartbeats, status pages, and telemetry sources
Disconnecting
Disconnect Better Stack in Praxen Inc., then revoke the API tokens in Better Stack.
Register Better Stack alerts to Praxen Inc. alongside your Terraform-managed resources.
Alert delivery lives on a single outgoing webhook named praxen that covers every incident, so Terraform-managed monitors need nothing added: they are covered automatically. Leave the praxen outgoing webhook in place; Praxen Inc. creates and removes it with the integration.
Disconnect
Disconnecting stops every sync and check and deletes the credentials Praxen Inc. held. Everything Praxen Inc. set up in Better Stack is removed as well; nothing is left behind.
praxen integration disconnect <id>Tools
7Operations agents can perform in threads.