Skip to content
Super 1.7.0 is production-ready — transactional installs with automatic rollback, cron runtime caps (kill_after_secs), and panic-free input handling. See what’s new →
Documentation Center
Orchestration
Events

Events

Events are the daemon’s structured signal layer. Every meaningful thing that happens — a process crash, a recovery, a cron run, a daemon startup — is emitted as an event, recorded to persistent history, and can trigger reactions.

The event system has three layers:

      ① EMIT ──▶ ② RECORD ──▶ ③ REACT
   what happens   event history   real-time actions
   (event types)  (events.db)     (hooks / notifications)
LayerPageWhat it answers
① EmitEvent TypesWhat events exist? What does each payload contain?
② RecordEvent HistoryWhere are events stored? How long are they kept? How do I search and audit them?
③ ReactEvent Hooks · Alerting (notify) 💎OSS: scripts or webhook via [[event_hooks]]. Licensed: optional notify plugin for IM + storm suppression (same events, separate config).

Quick orientation

  • Which events are recorded? All of them — crashes, OOM kills, backoff retries, recoveries, health restarts, cron runs, queue drops, and daemon startup/shutdown. See Event Types.
  • Where is the history stored? A SQLite database (default data/events.db, WAL mode) with configurable retention. See Event History.
  • How do I look at it? super events <name> from the CLI, or the events API. See Event History — Querying.
  • How do I react in real time? One OSS mechanism: [[event_hooks]] in super.toml — each entry is either a local script (command) or a webhook POST (url), not both. For production IM alerting with templates and storm suppression, add the licensed notify plugin (conf/notify.toml); it uses the same events and can run alongside hooks. See Event Hooks vs Event Notifications.
  • Per-program start/stop hooks? Those are a different mechanism (lifecycle hooks) — see Lifecycle Hooks.

OSS vs licensed

Event hooks ([[event_hooks]]) are OSS — scripts or basic webhook POST. The licensed notify plugin is a separate alerting layer on the same events (IM templates, channels, storm suppression). Configure hooks in super.toml and alerting in conf/notify.toml; both can be active. See the feature matrix.

Related