Skip to main content
Sazabi watches your data and opens an issue when it detects a problem worth your attention. An issue arrives already investigated: it names what happened, why, and the evidence from your own logs, and it gives your team one place to respond. You don’t write monitors, thresholds, or alert rules. Issues cover reliability, correctness, security, and efficiency problems. See Issues.

What it needs

A project that receives your logs. Sazabi can only report what your logs contain, so the more of your stack you send, the more it can see. Notifications need at least one connected channel, such as Slack or a paging tool.

Set it up

1

Send your logs

Hand setup to your coding agent or run one command. See Quickstart. To add more of your stack, see Send data.
2

Choose where issues go

Connect a channel under Settings > Integrations, then add a delivery rule so the issues you care about reach the right people. See Route notifications. To page whoever is on call, see Page your on-call.
3

Open your first issue

Read what Sazabi found, ask a follow-up in the issue’s thread, and resolve it. See Run your first investigation. List open issues from a terminal with npx -y @sazabi/cli@latest issues list --status open.

Go deeper

  • Sensors: the standing questions the Sazabi agent keeps asking about your logs.