Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.superform.xyz/llms.txt

Use this file to discover all available pages before exploring further.

SuperformOS Alerts — notification channels and vault alert routing Alerts connect vault events to notification destinations. The shipped flow centers on notification-channel creation, listing, and vault binding. Treat alert delivery as operational plumbing: channel setup first, event history and routing second.

Notification channels

A notification channel defines where Erebor can send vault events.
FieldDescription
providerChannel provider or transport.
nameOperator-facing channel name.
configProvider-specific destination config. Sensitive values should be redacted in UI.
created_byCreator metadata.
created_at / updated_atAudit timestamps.

Channel endpoints

EndpointMethodDescription
/api/v1/notification-channelsGETList channels available to the operator.
/api/v1/notification-channelsPOSTCreate a channel.
/api/v1/vaults/{chain_id}/{vault_address}/notification-channelsGETList channels bound to a vault.
/api/v1/vaults/{chain_id}/{vault_address}/notification-channels/{channel_id}POSTBind a channel to a vault.
/api/v1/vaults/{chain_id}/{vault_address}/notification-channels/{channel_id}DELETEUnbind a channel.

Operator flow

  1. Create a channel with a clear name.
  2. Bind it to the relevant vault.
  3. Trigger or wait for a low-risk event to confirm delivery.
  4. Keep at least one secondary notification path for high-value vaults.

Events to monitor

Common alert categories include upkeep shortfall, PPS staleness, failed keeper runs, session-key readiness, emergency pause/unpause, emergency liquidity exit arm/stop, merkle publish failures, and repeated OMS execution failures.

Troubleshooting

SymptomCheck
Channel exists but receives nothingConfirm it is bound to the vault.
Sensitive destination appears in UIRedact config display and rotate destination if leaked.
Alerts are noisyTune event thresholds before muting the channel.
Incident alert missingCheck audit logs and notification-channel binding first.