Alerts
Availability
Open core · self-host + all Splyntra Cloud plans
Alerts turn signals you already collect — risk and spend — into notifications, so you hear about a problem instead of finding it later in a table.
Rule types
| Rule type | Fires when |
|---|---|
| Risk threshold | A run's risk score crosses a level you set (for example, any HIGH or CRITICAL run). |
| Cost overrun | Spend crosses a budget or threshold. See Costs. |
Channels
Alerts are delivered through channels configured on the collector via environment variables:
| Channel | Collector env |
|---|---|
| Webhook | ALERT_WEBHOOK_URL |
| Slack | ALERT_SLACK_WEBHOOK_URL |
SMTP_* settings |
See Configuration for the full collector env reference. If a channel isn't configured, rules that target it simply don't deliver.
The wizard's default rule
The Connect an agent wizard has an Alerts step with a checkbox — on by default — that creates a HIGH/CRITICAL risk-threshold rule for the new agent. That gives every freshly connected agent baseline coverage: if a run scores in the high or critical band, you're notified. Tune or remove it from the Alerts screen afterward.
Next steps
- Costs — budgets that feed cost-overrun alerts.
- The risk score — how HIGH and CRITICAL are defined.
- Configuration — wire up the alert channels.