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

# Better Stack

> Connect Better Stack on-call so Sazabi can open and resolve Better Stack incidents for issues.

## Supported capabilities

MCP connectorCore integration

* **MCP connector**: [Better Stack](https://docs.sazabi.com/catalogs/mcp-connectors/better-stack.md) — Give the Sazabi agent tools to investigate incidents, monitors, and log sources, and build telemetry queries directly from agent conversations.
* **Core integration**: [Better Stack](https://docs.sazabi.com/catalogs/integrations/better-stack.md#core-integration) — Connect Better Stack on-call so Sazabi can open and resolve Better Stack incidents for issues.

Each connection method has its own setup and permissions. Connecting one method does not enable the others.

## Core integration

## About

Connecting Better Stack lets Sazabi route issues to Better Stack on-call, so they open Better Stack incidents and page your escalation. Better Stack is a shared [notification channel](https://docs.sazabi.com/guides/detect/notifications.md).

When you route to Better Stack, you can target the team's **default** escalation or a specific **escalation policy**. Sazabi opens one Better Stack incident when an issue opens and resolves it when the issue is resolved or ignored. Severity mapping decides how loudly Better Stack alerts: critical issues call, text, push, and email; high issues text, push, and email; medium issues push and email; low issues are skipped by default.

## Prerequisites

* A Better Stack **team API token**.
* The email of a member of that Better Stack team. Better Stack shows it as the requester on incidents Sazabi opens.
* Organization admin access in Sazabi.

## Set up in the dashboard

**Step 1**

### Create a Better Stack API token

In Better Stack, go to **Settings > API tokens** and create a team-scoped token. Copy it.

**Step 2**

### Open the Better Stack integration

In the dashboard, go to [**Settings > Integrations > Better Stack**](https://app.sazabi.com/settings/integrations/better-stack).

**Step 3**

### Enter the token and requester email

Paste the token, enter the email of a team member, and connect. Sazabi checks the token by listing your escalation policies so you can pick a routing target.

**Step 4**

### Add a delivery rule

On the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that
routes an event type to a Better Stack destination. See
[Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Set up with the CLI

You can also connect Better Stack with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/integrations.md)).

Better Stack is an API-key provider, so pass the token as the `apiToken` credential and the requester as `requesterEmail`. Read the token from an environment variable rather than pasting it inline:

```bash theme={"system"}
export BETTER_STACK_API_TOKEN=...   # your Better Stack team API token
sazabi integrations connect better_stack \
  --credentials "{\"apiToken\":\"$BETTER_STACK_API_TOKEN\",\"requesterEmail\":\"oncall@example.com\"}"
```

Then add a delivery rule so issues reach Better Stack — from the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, or with the CLI (`sazabi notifications delivery-rules create`; see [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md#delivery-rules)). Run `sazabi integrations list` to confirm the connection, or `sazabi integrations providers --json` to see each provider's credential fields.

## Notifications

Use Better Stack as a delivery destination for issue events: on the project [**Settings > Notifications**](https://app.sazabi.com/settings/project-notifications) page, add a delivery rule that routes an event type to a Better Stack destination. See [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md).

## Verify

With a delivery rule pointing at a Better Stack destination, trigger a test issue and confirm an incident opens in Better Stack within a minute. Resolve the issue and confirm the Better Stack incident resolves.

## Troubleshooting

**No incident in Better Stack** — Confirm the delivery rule names both the event type and the Better Stack destination, that no condition excludes the issue, and that the issue's severity isn't set to skip.

**Incident creation fails** — Better Stack requires the requester email to belong to the team. Reconnect with the email of a team member.

**Connection shows needs attention** — The API token may have been revoked. Create a new token in Better Stack and reconnect.

## Further reading

> [card] [Route notifications](https://docs.sazabi.com/guides/detect/notifications.md)
>
> Route issues to Better Stack with delivery rules.

> [card] [Rootly](https://docs.sazabi.com/catalogs/integrations/rootly.md)
>
> Another incident routing destination.

> [card] [Integrations](https://docs.sazabi.com/catalogs/integrations.md)
>
> Browse the full integration catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.