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 withnpx -y @sazabi/cli@latest issues list --status open.Go deeper
- How Sazabi detects issues: the group overview.
- Issues: what an issue is, how it differs from an alert or a monitor, types, and categories.
- Sensors: the standing questions the Sazabi agent keeps asking about your logs.
- Troubleshooting detection: why an issue wasn’t detected or why one incident became several.
- Issue lifecycle and severity: states, severity levels, and how to resolve, ignore, or reject an issue.
- Service status: the health of your services, drawn from open issues.
- Route notifications, File tickets, and Page your on-call: get issues to people and tools.
- Troubleshooting notifications: when a notification didn’t arrive or reached the wrong channel.