Connect your logs, then ask the Sazabi agent what is happening in production. It searches your data, correlates it, and answers in plain language with the evidence it found. You can begin with a question instead of creating a saved dashboard or writing a query.

<Cards>
  <Card title="Quickstart" href="/get-started/quickstart" description="Create a project, send your first log, and ask your first question in about 10 minutes." />

  <Card title="Connect your coding agent" href="/get-started/coding-agents" description="Investigate production from Claude Code, Cursor, Codex, and other agents." />

  <Card title="Setup checklist" href="/get-started/setup-checklist" description="The steps that take a new project to a working investigation surface." />

  <Card title="Concepts" href="/get-started/core-concepts" description="The day-zero ideas: threads, the agent, log sources, issues, and integrations." />
</Cards>

## What Sazabi does [#what-sazabi-does]

Most observability tools make you work for answers: know which dashboard to open, write the query, then correlate data across views. Sazabi inverts that. You describe the problem, and the Sazabi agent runs the queries, reads the results, and reports back.

```text
Why are checkout errors elevated right now?
What changed in the last hour that could explain this latency spike?
Show me the error logs for order 8842 from today.
```

Sazabi also watches your systems on its own. When it detects a problem worth tracking, it opens an issue and can notify your team — with the impact, the likely cause, and the evidence attached, not a raw threshold alert.

## How it works [#how-it-works]

<Steps>
  <Step>
    ### Connect your data [#connect-your-data]

    Send logs from any language, framework, or cloud — through OpenTelemetry, a native SDK, or a direct connection to platforms such as AWS CloudWatch, Google Cloud, and Vercel. Sazabi stores and indexes your logs in managed storage so they are ready to search.
  </Step>

  <Step>
    ### Get alerted, or ask [#get-alerted-or-ask]

    Sazabi detects issues in your data and notifies you through the channels you configure. You can also open a thread any time and ask a question in plain language.
  </Step>

  <Step>
    ### Get answers with evidence [#get-answers-with-evidence]

    The Sazabi agent responds with what it found — specific log lines, anomalies, and timing correlations — and shows the queries it ran so you can verify and dig deeper.
  </Step>
</Steps>

## Where to go next [#where-to-go-next]

<Cards>
  <Card title="Instrument" href="/guides/instrument" description="Connect log sources and get logs flowing into Sazabi." />

  <Card title="Investigate" href="/guides/investigate" description="Work in threads, use the agent's tools, and configure the sandbox." />

  <Card title="Detect" href="/guides/detect" description="Issues, automations, notifications, and status." />

  <Card title="Administer" href="/guides/administer" description="Organizations, members, access, keys, and billing." />

  <Card title="Catalogs" href="/catalogs/log-sources" description="Every log source, integration, MCP connector, and sandbox CLI." />

  <Card title="Reference" href="/reference/api" description="CLI, API, SDKs, and the MCP server." />
</Cards>