Skip to main content
When Sazabi detects a problem in your data, it opens an issue and investigates it. This walkthrough takes one issue from the report to a question of your own. It follows the Quickstart. New projects also start with Test issue: Checkout error spike, created during setup to show the shape of an issue. Use a real issue here. If you have none yet, Search logs works on any data you have sent.

​
Find the issue

Copy the ID of the issue you want.

​
Read the root cause

The output shows the issue’s details and description, then its activity. The agent’s report is printed with the entry that created the issue and holds what happened, why it happened, and the evidence. A Thread: line gives the command that opens the issue’s thread, with its ID.

​
Ask a follow-up

Ask the agent anything the report leaves open, such as what changed before the issue opened.
Use the thread ID from the Thread: line:
--wait prints the agent’s reply when it finishes. To read the whole thread afterwards, run npx -y @sazabi/cli@latest threads get your-thread-id.

​
Search the logs behind it

Ask a question about the logs from around the time the issue opened. Use the component’s name from the issue.
The answer comes with its results, the time window, and a query ID that reruns the same query later. See Search logs.

​
Verify

The agent’s reply cites log lines from around the time the issue opened. In the CLI, the logs ask answer lists matching lines with their service and severity.

​
Next steps

Route notifications

Send issue alerts to the channels your team watches.

Hand off a root cause

Give an issue’s root cause to your coding agent to fix.