---
title: "Sazabi"
description: "Give agents access to Sazabi issues, logs, and investigations."
canonical_url: "https://hoplite.sh/docs/integrations/sazabi"
markdown_url: "https://hoplite.sh/docs/integrations/sazabi.md"
---

# Sazabi
URL: /docs/integrations/sazabi
LLM index: /llms.txt
Description: Give agents access to Sazabi issues, logs, and investigations.
Related: /docs/integrations, /docs/agent/tools

# Sazabi

Connect Sazabi under **Settings → Integrations** to let agents investigate production issues with `sazabi_control`. The tool is available only while the current Hoplite workspace has a Sazabi connection.

## Setup

1. In Sazabi, create an organization secret key under **Settings → Secret keys**. Public ingestion keys, user credentials, and partner credentials aren't supported.
2. As a Hoplite workspace administrator, open the Sazabi integration and paste the secret key into the connection form. Hoplite validates the key with Sazabi before storing it encrypted. Don't paste keys into a thread.
3. Keep issue changes disabled for read-only access, or enable them when agents should be able to triage issues with approval.

The connection grants agents access to the connected Sazabi organization's projects. It isn't restricted to one repository, and it doesn't create a separate Sazabi project binding. Use an organization whose data is appropriate for members of this Hoplite workspace.

## Agent operations

Agents can inspect the connection, list projects, search and read issues, query logs, and read investigation threads and messages. Project-scoped operations use a Sazabi project ID from the project list. List operations support bounded pages and cursors.

When issue changes are enabled, agents can resolve, reopen, ignore, mute, and unmute issues. Each change requires approval. After issue changes are disabled, subsequent runs advertise only read operations, and further writes are blocked during execution even in an already-running thread.

Disconnecting removes the tool from subsequent runs and blocks further calls from active runs. Rotate a key by reconnecting with its replacement; an invalid replacement doesn't remove the working connection.

This integration doesn't ingest telemetry or automatically start Hoplite threads from Sazabi alerts.

## API reference

The integration uses Sazabi's [public REST API](https://docs.sazabi.com/reference/api) at `https://api.sazabi.com/v1`, following its [published OpenAPI contract](https://api.sazabi.com/openapi.json). Requests use the encrypted organization secret on the server; the browser and model never receive it.

## Sitemap

See the full [sitemap](/docs/sitemap.md) for all pages.
Well-known sitemap: [/docs/.well-known/sitemap.md](/docs/.well-known/sitemap.md).