> ## Documentation Index
> Fetch the complete documentation index at: https://docs.duckie.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Alerts
> Configure guardrail, tool failure, and agent-triggered alerts
Alerts help your team notice important agent events and follow up quickly.
Use **Analyze -> Alerts** to manage alert definitions and review triggered alerts.
## Alert Types
| Alert type | What triggers it | Use it for |
| ------------------- | ----------------------------------------------------- | ---------------------------------------------------------------------- |
| Guardrail Violation | A selected guardrail is violated | Safety, policy, compliance, or escalation events |
| Tool Failure | A selected tool fails during a run | Broken integrations, failed writes, or important workflow dependencies |
| Agent Triggered | An agent calls Create Alert with the alert name or ID | Situations that require judgment, review, or team visibility |
## Create An Alert Definition
Go to **Analyze -> Alerts**.
Click **Create Alert**.
Select **Guardrail Violation**, **Tool Failure**, or **Agent Triggered**.
For a guardrail alert, choose the guardrail. For a tool failure alert, choose the tool. For an Agent Triggered alert, enter the alert name and description.
Choose **Critical**, **Warning**, or **Info**. Add email recipients or Slack channels when the alert should notify a team.
Save the alert definition. Enabled definitions can trigger new alerts.
## Agent Triggered Alerts
Agent Triggered alerts let an agent raise a configured alert during a run.
Use them when the agent can detect that something needs human visibility, but the condition is not tied to one guardrail or one tool failure. Examples include:
* a billing exception that needs review
* a customer request that matches a high-priority escalation pattern
* a failed multi-step process where the right next step is human triage
* a case that should appear in an operations queue
For each Agent Triggered alert:
* Use a clear, unique name. Agents can trigger the alert by name or ID.
* Write a description that explains when the agent should use it.
* Choose severity based on the operational urgency.
* Configure email recipients or Slack channels when someone should be notified.
Then enable the **List Alerts** and **Create Alert** Duckie tools for the agent or flow that should trigger it. Create Alert is a write action because it creates a visible alert record and can notify configured recipients.
Example agent instruction:
```text theme={null}
If the customer reports a billing exception that cannot be resolved with the available tools,
call List Alerts and then Create Alert for Billing Review Needed.
Include a concise message body with the customer issue, attempted checks, and recommended next step.
```
## Triggered Alert History
Triggered alerts appear in the alert history with severity, status, type, source details, related run or ticket context when available, and timestamps.
Alert statuses are:
| Status | Meaning |
| ------------ | ---------------------------------------- |
| Unread | The alert has not been handled yet |
| Acknowledged | Someone has seen it and is investigating |
| Resolved | The issue was handled |
| Dismissed | The alert no longer requires action |
Use alert history with **Analyze -> Runs** when you need to inspect the run, tool calls, and context that produced the alert.
## Manage Alert Definitions
From the configured alerts list, you can edit, enable, disable, or delete alert definitions.
Disabling an alert definition stops new alerts from being created from that definition. Existing triggered alerts remain in alert history.
## Related Docs
Learn how List Alerts and Create Alert work.
Configure escalation rules and restrictions.
Inspect the run behind an alert.
Control which tools each agent can use.