Alert Threads

Every alert in Sazabi exists within a conversation context. Understanding the relationship between source threads and alert threads helps you investigate issues effectively and maintain context across your team.

Source thread

The source thread is the investigation where Chat first detected the issue and triggered the alert. This could be:

• A conversation you started asking about an anomaly
• An automated investigation triggered by monitoring
• A background analysis that surfaced a problem

The source thread contains the full context of how the issue was discovered, including:

• The questions that led to the investigation
• The queries the assistant ran
• The data it analyzed
• The reasoning that led to the alert

Alert thread

When an alert is created, Sazabi also creates a dedicated alert thread. This thread is separate from the source thread and serves as a focused space for:

• Viewing the alert card with full details
• Continuing investigation specific to the alert
• Collaborating with teammates on the response
• Tracking resolution progress

The alert thread includes:

• The alert card showing name, severity, what happened, why, and how to fix
• A link back to the source thread for context
• Space for follow-up questions and investigation

Navigation between threads

You can move between source and alert threads easily:

From source to alert

In the source thread, when the assistant creates an alert, you see:

• A card summarizing the alert
• A link to open the dedicated alert thread
• The current status of the alert (open, muted, resolved)

From alert to source

In the alert thread, the alert card includes:

• A "View source investigation" link
• Context about when and how the alert was triggered
• The investigation path that led to the alert

This bidirectional navigation ensures you can always trace an alert back to its discovery context or jump to the focused alert space from an investigation.

Continuing investigation

When you receive an alert notification (in Slack, email, or the dashboard), clicking through takes you to the alert thread. From there, you can:

Ask follow-up questions

Continue the conversation in the alert thread to dig deeper:

What else was happening around the time this error started?
Show me the specific requests that failed.
Are there any related issues in our payment service?

The assistant has context about the alert and can investigate further.

Access related data

The assistant can pull additional logs, traces, and metrics relevant to the alert without you needing to re-explain the context.

Collaborate with teammates

Share the alert thread link with colleagues. They can see the full context and add their own questions or observations to the conversation.

Best practices

• Start in the alert thread. When responding to a notification, the alert thread gives you focused context for that specific issue.

• Visit the source thread for history. If you need to understand how the issue was discovered or what other context surrounded it, follow the link to the source investigation.

• Keep investigation in the alert thread. Post-alert investigation belongs in the alert thread, keeping it associated with the issue being tracked.

• Use threads for handoffs. When passing an issue to a teammate, share the alert thread link. They get the alert context plus the conversation history.