Slack & incident channels
See Slack channels for the full guide. Key options here:| Setting | Description |
|---|---|
| Auto-create channel | Create a dedicated Slack channel for every new incident |
| Channel name template | Use {{id}}, {{title}}, {{severity}}, {{date}} placeholders |
| General notification channel | Announce new incidents in a shared #incidents channel |
| Archive channel after resolution | Auto-archive the dedicated channel N days after close |
Auto-create incident rules
Rules let Obsy automatically create incidents when alerts arrive. Each rule has:- Name — a label for your own reference
- Enabled toggle — turn individual rules on or off
- Alert severity — Critical, Warning, or Info
- Alert source — Datadog, Grafana, New Relic, or Any
- Service filter — limit to a specific service name (leave blank for any)
Example rules
| Rule | Severity | Source | Service |
|---|---|---|---|
| All critical Datadog alerts | Critical | Datadog | (any) |
| Payment service on Grafana | Warning+ | Grafana | payment-service |
| Any critical alert | Critical | Any | (any) |
Notification channels
Set how Obsy notifies your team when an incident is created or updated.| Channel | What it does |
|---|---|
| Slack | Posts to the configured general channel (requires Slack connected) |
| Sends email to all org members with Admin or Owner role |