# Better Stack AI integration on Definable

> Better Stack provides monitoring, logging, and incident management solutions to help teams ensure the reliability and performance of their applications.

## What this connects

Better Stack provides monitoring, logging, and incident management solutions to help teams ensure the reliability and performance of their applications.

Vendor: https://betterstack.com/

## Tools available

**117** tools available. First 12:

- `BETTER_STACK_ACKNOWLEDGE_INCIDENT` — Acknowledge Incident — Tool to acknowledge an ongoing incident. Use when you need to mark an incident as being worked on, which prevents further escalations. Acknowledging an incident signals that someone is actively addressing the issue.
- `BETTER_STACK_CREATE_ESCALATION_POLICY` — Create Escalation Policy — Creates a new escalation policy for incident management. Escalation policies define who gets notified and in what order when incidents occur. Supports multiple step types: 'escalation' (notify members), 'instructions' (guidance text), 'time_branching' (route by schedule), and 'metadata_branching' (route by incident metadata). For escalation steps, a valid urgency_id from the Severities API is required.
- `BETTER_STACK_CREATE_HEARTBEAT` — Create Heartbeat — Tool to create a new heartbeat monitor for cron jobs and scheduled tasks. Use when you need to set up monitoring for a service that should send regular heartbeat signals.
- `BETTER_STACK_CREATE_HEARTBEAT_GROUP` — Create Heartbeat Group — Tool to create a new heartbeat group. Use when you need to organize related heartbeat checks under a single, logical group. Example prompt: "Create a new heartbeat group named 'Backend services'."
- `BETTER_STACK_CREATE_INCIDENT` — Create Incident — Tool to create a new incident and alert the on-call person. Use when you need to manually report an incident or trigger escalation workflows. The incident will be routed according to the specified escalation policy or default team settings.
- `BETTER_STACK_CREATE_INCIDENT_COMMENT` — Create Incident Comment — Tool to create a new comment on an incident. Use when you need to add documentation, updates, or notes to an existing incident in Better Stack.
- `BETTER_STACK_CREATE_METADATA` — Create Metadata — Tool to create or update a metadata record for a resource. Metadata provides key-value associations for resources like monitors, heartbeats, or incidents. Use when you need to tag or annotate resources with custom data. Existing values for the specified key will be completely replaced.
- `BETTER_STACK_CREATE_MONITOR` — Create Monitor — Tool to create a new uptime monitor for a URL or service. Use when you need to set up monitoring for websites, APIs, servers, or network services. Supports multiple monitor types including HTTP/HTTPS status checks, keyword monitoring, ping, TCP/UDP, email protocols, DNS queries, and browser automation with Playwright.
- `BETTER_STACK_CREATE_MONITOR_GROUP` — Create Monitor Group — Tool to create a new monitor group. Use when you need to organize related monitors under a single, logical group for better dashboard organization.
- `BETTER_STACK_CREATE_ON_CALL_SCHEDULE` — Create On-Call Schedule — Tool to create a new on-call schedule. Use when you need to set up a new on-call calendar for managing team rotations.
- `BETTER_STACK_CREATE_OUTGOING_WEBHOOK` — Create Outgoing Webhook Integration — Tool to create a new outgoing webhook integration. Use when you need to register an endpoint to receive event notifications from Better Stack.
- `BETTER_STACK_CREATE_POLICY_GROUP` — Create Escalation Policy Group — Tool to create a new escalation policy group. Use when you need to organize related escalation policies under a single logical group.

## Auth

Auth schemes: `API_KEY`.

## How agents use Better Stack

Inside a Definable workflow, Better Stack is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Better Stack** — the Researcher (GPT-5.5) pulls context from Better Stack (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Better Stack** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Better Stack (create record, post message, draft email).
- **Designer / Engineer → Distributor → Better Stack** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Better Stack (attach file, open PR comment, post status).

The Verifier checks every Better Stack call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- server monitoring — https://definable.ai/apps/category/server-monitoring/

## Related

- HTML page: https://definable.ai/apps/better_stack/
- Same category (server monitoring): https://definable.ai/apps/category/server-monitoring/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt