Alerts
Alerts help teams respond before AI usage becomes expensive, unreliable, or hard to explain.
Alephant alerts should point back to the relevant workspace, department, member, agent, Virtual Key, policy, request, or run trace so operators can investigate quickly.
Alert Types
Severity Levels
Budget Alerts
Budget alerts can apply to:
- Workspace budgets
- Department budgets
- Agent budgets
- Member budgets
- Virtual Key budgets
- Paid endpoint or workflow spend limits
Common thresholds are warning, critical, and hard stop. A warning should notify operators; a hard stop should block or pause the relevant traffic according to policy.
Anomaly Alerts
Usage anomaly alerts are useful when an agent or workflow changes behavior unexpectedly:
- Request volume increases sharply.
- Token usage per request grows.
- A workflow starts retrying repeatedly.
- A fallback route becomes the primary route.
- A paid endpoint begins losing margin per call.
The investigation path should start from the alert and move into logs, run traces, analytics, and policy history.