> ## 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.

# Issue detection

> How Sazabi finds problems in your data and opens issues, what it needs to do that, and where to set it up.

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](https://docs.sazabi.com/detect/issues.md).

## 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

**Step 1**

### Send your logs

Hand setup to your coding agent or run one command. See [Quickstart](https://docs.sazabi.com/get-started/quickstart.md). To add more of your stack, see [Send data](https://docs.sazabi.com/send-data.md).

**Step 2**

### Choose where issues go

Connect a channel under [**Settings > Integrations**](https://app.sazabi.com/settings/integrations), then add a delivery rule so the issues you care about reach the right people. See [Route notifications](https://docs.sazabi.com/triage/notifications.md). To page whoever is on call, see [Page your on-call](https://docs.sazabi.com/triage/on-call.md).

**Step 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](https://docs.sazabi.com/get-started/first-investigation.md). List open issues from a terminal with `npx -y @sazabi/cli@latest issues list --status open`.

## Go deeper

* [How Sazabi detects issues](https://docs.sazabi.com/detect.md): the group overview.
* [Issues](https://docs.sazabi.com/detect/issues.md): what an issue is, how it differs from an alert or a monitor, types, and categories.

- [Sensors](https://docs.sazabi.com/detect/sensors.md): the standing questions the Sazabi agent keeps asking about your logs.

* [Troubleshooting detection](https://docs.sazabi.com/detect/troubleshooting.md): why an issue wasn't detected or why one incident became several.
* [Issue lifecycle and severity](https://docs.sazabi.com/triage/lifecycle.md): states, severity levels, and how to resolve, ignore, or reject an issue.
* [Service status](https://docs.sazabi.com/triage/status.md): the health of your services, drawn from open issues.
* [Route notifications](https://docs.sazabi.com/triage/notifications.md), [File tickets](https://docs.sazabi.com/triage/tickets.md), and [Page your on-call](https://docs.sazabi.com/triage/on-call.md): get issues to people and tools.
* [Troubleshooting notifications](https://docs.sazabi.com/triage/troubleshooting.md): when a notification didn't arrive or reached the wrong channel.


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