The Alerts page provides real-time monitoring of vault health events. Alerts are generated by the monitoring subsystem when vault conditions breach configured thresholds. Each alert carries a severity level and follows a defined lifecycle.
Alert Summary
The top section displays aggregate counts across all alerts for the selected vault:
By Status:
| Status | Description |
|---|
| Active | Unacknowledged alerts requiring attention |
| Acknowledged | Alerts seen by a manager but not yet resolved |
| Resolved | Alerts that have been addressed and closed |
| Total | Sum of all alerts |
| Severity | Description |
|---|
| Critical | Immediate action required — vault operations may be degraded or halted |
| Warning | Attention needed — conditions may escalate if not addressed |
| Info | Informational — parameter changes, scheduled maintenance, non-urgent notices |
Alert Lifecycle
Every alert follows a three-state lifecycle:
active → acknowledged → resolved
- Active — The condition has been detected and no manager has responded yet. Active alerts appear prominently in the dashboard.
- Acknowledged — A manager has clicked Acknowledge to signal awareness. The alert remains open but is no longer flagged as unattended.
- Resolved — A manager has clicked Resolve to close the alert, indicating the underlying issue has been addressed.
Alert History
The Alert History section displays all alerts in a tabbed view: Active, Acknowledged, and Resolved. Each alert record shows:
| Field | Description |
|---|
| Alert Type | Category of the alert (e.g., PPS Staleness Warning) |
| Severity | Critical / Warning / Info |
| Source | The vault and chain that triggered the alert |
| Message | Human-readable description of the condition |
| Timestamp | When the alert was created |
| Acknowledged By | Wallet that acknowledged (if applicable) |
| Resolved By | Wallet that resolved (if applicable) |
Alert Types
| Alert Type | Severity | Trigger Condition |
|---|
| PPS Staleness Warning | Warning | PPS has not been updated within the configured expiration window. Validator network may be experiencing issues. |
| PPS Staleness Critical | Critical | PPS staleness has exceeded the critical threshold. Vault operations are blocked. |
| High Redemption Queue | Warning | Pending redemption requests exceed the configured queue depth threshold. |
| Low Gas Balance | Critical | Keeper gas balance is critically low. Operations may fail. |
| Low Upkeep Balance | Warning | $UP upkeep balance is approaching the minimum threshold. |
| Keeper Service Down | Critical | One or more keeper services have stopped responding. |
| Service Success Rate Low | Warning | Keeper service success rate has dropped below the configured threshold. |
| Strategy Error | Warning | A strategy has entered the ERROR state. |
Webhook Integrations
Alerts can be forwarded to external systems via webhook integrations. Webhooks support three providers:
| Provider | Description |
|---|
| Slack | Posts alert notifications to a Slack channel via incoming webhook URL |
| PagerDuty | Triggers PagerDuty incidents for critical alerts via Events API v2 |
| Discord | Posts alert notifications to a Discord channel via webhook URL |
Configure at least one webhook for critical alerts on production vaults. PagerDuty is recommended for on-call rotation workflows. Slack or Discord work well for team-wide visibility.
API Reference
Alert data is surfaced via the Erebor audit log (GET /api/v1/audit/logs) and vault analytics endpoints. Webhook configuration is managed internally and not currently exposed via a public REST API. Refer to the Alerts page in the curator UI for current alert status.
| Endpoint | Method | Backend | Description |
|---|
GET /api/v1/audit/logs | GET | Erebor | Query audit trail for vault events |
GET /api/v1/audit/logs/{id} | GET | Erebor | Single audit log entry |
GET /api/v1/audit/export | GET | Erebor | Export audit logs (CSV or JSON via Accept header) |
GET /api/v1/vaults/{chain_id}/{address}/analytics/overview | GET | Erebor | Vault health overview metrics |
