Setup checklist

Work through this list to get a Sazabi project fully set up. The same items appear as a setup checklist on your project in the dashboard, where each one links straight to the page that completes it and marks itself done once the underlying step is in place — you never check anything off by hand.

You do not have to do every item. The first two make the project useful; the rest are worth doing if they fit how your team works. Do them in any order — skipping one does not block the others.

Get your logs flowing

• Connect a log source. Until logs are flowing, the agent has nothing to investigate. Get your intake URL and connect a source under Settings > Log streams. The Quickstart walks through the fastest way to do it.
• Confirm logs are arriving. Under Settings > Log streams, check that your source shows recent intake activity so you know the agent has data to search.
• Add more sources. Connect the rest of your logs, metrics, and traces so investigations can draw on your whole stack, not one service alone.

Connect your code

• Connect your code host. Connect Sazabi to your code host (such as GitHub or Bitbucket) under Settings > Integrations so investigations can also read your code.
• Link a repository. Under Settings > Code, link at least one repository so the agent can search it during investigations. Skip both steps if you do not want the agent reading your code — you can come back later.

Connect chat

• Connect your chat platform. Connect your team's chat platform (such as Slack or Microsoft Teams) under Settings > Integrations so your team can ask the agent from chat.

Configure issue notifications

• Route issue notifications. Under Settings > Notifications, choose where issue alerts and agent summaries land — a chat channel, email, or another destination — so the right people hear when something goes wrong in production. Skip if you do not want issue notifications yet.

Set up your team and organization

• Invite your team. Add a teammate under Settings > Members so your whole team can collaborate. Skip if you are evaluating on your own.
• Set up auto top-up. Turn on automatic credit reloads under Settings > Billing so investigations never pause when your balance runs low.

Customize the Sazabi agent

• Add MCP connectors. Give the agent tools from external services under Settings > MCP connectors. Only needed if you want it to reach beyond your logs and code.
• Customize the sandbox. Add environment variables or a setup script under Settings > Sandbox CLIs if your investigations need them.

Try the full workflow

• Send your first message. Open a thread in your project and ask the agent a question, so you see an answer against your own data.
• Resolve your first issue. Open an issue from the inbox, ask the agent to investigate, and follow its recommendation through to resolution.
• Visit your status page. Open your project's status page from the sidebar to see how Sazabi monitors the health of your services.

The exact items you see in the dashboard depend on how you signed up and what you have already connected — some steps arrive pre-completed for accounts that are already verified or joined through an invite.

Further reading