Discord Integration
Send TigerOps alert notifications and AI incident summaries to Discord channels. Rich embeds, severity colors, @mentions, and recovery messages — all via webhook.
How It Works
Create a Discord Webhook
In your Discord server, go to Channel Settings > Integrations > Webhooks and create a new webhook. Copy the webhook URL.
Add the Webhook to TigerOps
Paste the Discord webhook URL in TigerOps under Settings > Alerting > Discord. Configure the channel, severity filter, and notification format.
Configure Severity Routing
Route critical alerts to a dedicated #incidents channel with @here mention. Send warnings to #monitoring. Route recovery messages to the same channel as the original alert.
Enable Rich Embeds
TigerOps sends Discord embeds with color-coded severity, metric sparklines, correlated event timeline, and direct deep-link buttons to the TigerOps incident page.
What You Get Out of the Box
Rich Embed Notifications
Discord embed messages with severity-colored sidebars (red for critical, yellow for warning, green for recovery), metric values, and clickable action buttons.
AI Incident Summaries
The TigerOps AI root cause summary is included in the Discord message body — giving on-call engineers immediate context without needing to log into another tool.
Multi-Channel Routing
Route different alert types to different Discord channels. Infrastructure alerts go to #infra-alerts, application errors to #app-errors, and SLO breaches to #slo-incidents.
@mention Support
Configure TigerOps to @mention specific Discord roles or users for critical alerts. Mention @oncall-engineers for P1 incidents and @team-leads for SLO breaches.
Recovery Notifications
When an alert resolves, TigerOps sends a green recovery message to the same channel with the total incident duration and a link to the post-incident summary.
Alert Digest Mode
Enable digest mode to batch multiple alerts into a single Discord message every N minutes, reducing notification noise during incident storms.
Discord Webhook Integration Config
Configure multi-channel routing with severity filtering and @mention support.
# tigerops-discord-config.yaml — Discord notification routing
integrations:
discord:
# Primary incidents channel — critical alerts only
- name: incidents-channel
webhookUrl: "${DISCORD_INCIDENTS_WEBHOOK}"
minSeverity: critical
mentionRoles:
- "1234567890" # @oncall-engineers role ID
embedColor:
critical: 0xFF0000
warning: 0xFFAA00
resolved: 0x00CC44
# General monitoring channel — all alerts
- name: monitoring-channel
webhookUrl: "${DISCORD_MONITORING_WEBHOOK}"
minSeverity: warning
digestMode:
enabled: true
intervalMinutes: 5
maxAlertsPerDigest: 10
routing_rules:
- match:
labels:
env: production
severity: critical
discord:
channel: incidents-channel
includeAISummary: true
includeMetricChart: true
buttons:
- label: "View Incident"
url: "{{ .IncidentURL }}"
- label: "Acknowledge"
url: "{{ .AckURL }}"
- match:
labels:
env: production
discord:
channel: monitoring-channel
includeAISummary: true
mute_schedule:
- channel: monitoring-channel
start: "00:00"
end: "08:00"
timezone: "America/New_York"
days: [saturday, sunday]Common Questions
Can TigerOps send alerts to multiple Discord servers?
Yes. Add multiple Discord webhook URLs in TigerOps — one per server or channel. Each webhook can have independent severity filters and routing rules, so different servers receive different alert subsets.
Is a Discord bot required or can TigerOps use webhooks?
TigerOps uses Discord's incoming webhook API, which requires no bot installation. Just create a webhook in your Discord channel settings and paste the URL into TigerOps. No OAuth scopes or server permissions required.
Can I suppress certain alert types from going to Discord?
Yes. In the TigerOps Discord integration settings, configure severity filters (minimum severity to notify), label filters (only alerts with env=production), and mute schedules (no alerts during midnight to 8am).
Do recovery messages appear in the same channel as the alert?
Yes. TigerOps sends recovery messages to the same webhook URL that received the original alert, so they appear in the same Discord channel. The recovery message references the original alert by name for easy correlation.
Can TigerOps mention the current on-call person in Discord?
If your on-call schedule in TigerOps (or synced from PagerDuty/Opsgenie) maps to Discord user IDs, TigerOps can @mention the current on-call engineer directly in the critical alert message.
Your Team Is Already on Discord. Meet Them There.
AI summaries, rich embeds, and severity routing. Discord webhook setup takes under 2 minutes.