Core concepts
Alerts & channels
The briefing is the scheduled message. Alerts are the unscheduled ones — and they are deliberately hard to trigger, because a channel that cries wolf gets muted within a week.
The three message types
| Type | Fires when | Cooldown |
|---|---|---|
| Daily briefing | The project's delivery time comes round. | 20 hours |
| Critical alert | A critical signal is raised — a checkout error spike, a severe churn move. | 6 hours |
| Warning alert | A warning signal is raised. Off by default on every channel. | 12 hours |
Cooldowns are per channel and per type, so a noisy afternoon cannot turn into twenty Slack messages. Delivery failures are recorded and retried on the next cycle; one unreachable Slack workspace never blocks the other channels or another project.
Channels
Every channel carries the same content. Pick per project, and pick which severities each one is allowed to send.
| Channel | Set up with | Notes |
|---|---|---|
| Recipients under Project settings → Reports | Up to ten addresses. No account needed to receive one. | |
| Slack | An incoming webhook URL | A real test message is posted before the channel is saved — if Slack rejects it, it is not saved. |
| Discord | A channel webhook URL | Same confirmed test post before saving. |
| Webhook | Your own HTTPS endpoint | Receives the payload as JSON for anything you want to build on top. |
Setting up Slack or Discord
- 1In Slack, create an Incoming Webhook for the target channel. In Discord, use Channel settings → Integrations → Webhooks.
- 2In Seiton, open Project settings → Alerts and paste the webhook URL.
- 3Choose what that channel receives: the daily briefing, critical alerts, warning alerts, or any combination.
- 4Save. A test message is delivered immediately — nothing is stored until the channel accepts it.
Output only
Slack and Discord are delivery targets, never data sources. Nothing posted in those channels is read, and neither one can move a health dimension. Per-provider detail is on the Slack page and the Discord page.
Why so few alerts
- Only signals the engine classes as critical or warning can produce one. Ordinary movement goes into the briefing, not into your evening.
- A dimension without a trusted source raises nothing at all — silence from an unconnected source is not an incident.
- Warning alerts ship switched off. Turn them on per channel once you trust the critical ones.
Something here wrong or missing? hello@seiton.online