Notifications
Send deploys, outages, crash loops, alerts and finished jobs to Slack, a webhook or an email address, for the whole team or for one app.
A notification rule sends events to one channel: a Slack incoming-webhook URL, any webhook URL (JSON POST) or an email address. A rule covers either every app in the team or a single app.
Every new team starts with one rule: an email rule to the team owner’s address, covering deploy failures, offline servers, crash loops and apps down. Edit or delete it like any other rule under Settings → Team → Notifications.
Team rules
Settings → Team → Notifications. Pick a channel, paste the URL or address, choose a scope (All apps or one app) and tick the events you want:
| Event | When it fires |
|---|---|
| deploy ✗ / deploy ✓ | A deploy fails or succeeds |
| awaiting approval | A deploy is waiting for approval |
| offline | A server stops reporting in |
| crash loop | A process keeps restarting |
| disk high | A server is running out of disk, CPU or memory |
| app down | An app stops answering its uptime checks, or an uploaded certificate is close to expiring |
| costs | New waste found, spending spikes, or the month-end forecast goes over your budget (see Costs and savings) |
| log alerts | A saved log search matched too often |
| job backlog | Background jobs are backing up, and again when they’ve caught up |
| metric alerts | A metric alert fired, and again when it’s back to normal |
| data maintenance and server jobs | A maintenance window is coming up or finished, or a server job ended |
| imports, backups and moves finish | A long data job finished, or any one failed |
Each rule shows when it last delivered and whether that worked. Test sends a sample message, and you can disable a rule without deleting it.
Per-app rules
On an app, Settings → General → Notifications adds a rule for that app only, so a team that only cares about one app doesn’t hear about the rest. It has the same channels and the app-level events: deploy failed, deploy succeeded, app down, crash loop, job backlog, metric alerts, and imports, backups and moves finishing. There’s a send-test button, and each rule shows its last delivery.
Webhook payloads
Webhook rules get a JSON POST. Metric alerts, for example, carry event: "metric_alert", status (firing or resolved), metric, value and threshold. Deploy notes are included on deploy events.
For signed deploy events meant for your own systems, use Team → Webhooks (outbound webhooks). Those are separate from notification rules.
Limits
- Email is beta. Email only goes out when email sending is set up on Railyard’s side. For anything you rely on, add Slack or a webhook as well.
- Each rule has one destination. To notify two Slack channels, add two rules.