Alerts
Alerts turn product metrics into rule-based notifications.
Alert rule
Section titled “Alert rule”An alert contains:
- name;
- optional description;
- scope type;
- optional scope key;
- metric;
- operator;
- threshold;
- cooldown;
- active state.
Metrics
Section titled “Metrics”Supported metrics include:
- importance;
- confidence;
- sentiment.
Operators
Section titled “Operators”Rules can use:
- greater than or equal;
- less than or equal;
- greater than;
- less than;
- equal.
Scopes
Section titled “Scopes”Alerts can be scoped to a ticker, sector, wallet, or global event stream. A missing scope key can represent a broader rule, depending on the selected type.
Cooldown
Section titled “Cooldown”The cooldown prevents repeated delivery when several matching events arrive close together. It should be long enough to control noise but short enough for the monitoring objective.
Alert inspector
Section titled “Alert inspector”The detail view includes:
- summary;
- scope and condition;
- recent matching events;
- delivery history;
- acknowledgement state;
- editing controls;
- test and lifecycle actions.
Live delivery
Section titled “Live delivery”The Alerts page receives live updates, and alert notices can also appear in Live Pulse. Delivery availability depends on the configured channel; onboarding currently supports the available in-app channel.
Permissions
Section titled “Permissions”Creating, editing, toggling, testing, acknowledging, or deleting alerts requires the corresponding workspace permission.
Recommended practice
Section titled “Recommended practice”Combine importance and scope carefully. A global low-threshold alert is likely to be noisy. Start with a specific asset, wallet, or sector and a meaningful cooldown, then review delivery history before broadening it.