How to Set Up Slack Alerts for Website Downtime

Slack is where your team already communicates. Getting downtime alerts directly in Slack means faster response times and better team visibility. Here's how to set it up.

Why Slack for Alerts?

• Team visibility - Everyone sees issues immediately
• Quick response - No switching between apps
• Collaboration - Discuss incidents in threads
• History - Searchable alert archive
• Mobile - Get push notifications anywhere

Setting Up Slack Integration

Method 1: Native Integration

Most monitoring tools offer direct Slack integration:

1. Go to your monitoring dashboard
2. Navigate to Integrations or Notifications
3. Select Slack
4. Click "Connect to Slack"
5. Authorize the app for your workspace
6. Select the default channel

Method 2: Incoming Webhook

For more control, use webhooks:

Step 1: Create Incoming Webhook

1. Go to api.slack.com/apps
2. Click "Create New App" → "From scratch"
3. Name it (e.g., "WizStatus Alerts")
4. Select your workspace
5. Go to "Incoming Webhooks"
6. Toggle "Activate Incoming Webhooks" on
7. Click "Add New Webhook to Workspace"
8. Select the channel
9. Copy the webhook URL

Step 2: Add to Monitoring

Add the webhook URL to your monitoring service's notification settings.

Step 3: Test

Send a test alert to verify it works.

Configuring Alert Channels

Channel Strategy

Create dedicated channels for different purposes:

#alerts-production   - Critical production issues only
#alerts-staging      - Staging environment alerts
#alerts-all          - All alerts (for review)
#incidents           - Active incident discussion

Channel-Based Routing

Configure different monitors to alert different channels:

Message Formatting

Rich Slack Messages

Configure your monitoring tool to send formatted messages:

{
  "blocks": [
    {
      "type": "header",
      "text": {
        "type": "plain_text",
        "text": "🔴 Production API is DOWN"
      }
    },
    {
      "type": "section",
      "fields": [
        {"type": "mrkdwn", "text": "*Monitor:*\nProduction API"},
        {"type": "mrkdwn", "text": "*Status:*\nHTTP 500"},
        {"type": "mrkdwn", "text": "*Duration:*\n5 minutes"},
        {"type": "mrkdwn", "text": "*Location:*\nUS-East"}
      ]
    },
    {
      "type": "actions",
      "elements": [
        {"type": "button", "text": {"type": "plain_text", "text": "View Dashboard"}, "url": "https://..."},
        {"type": "button", "text": {"type": "plain_text", "text": "Acknowledge"}, "style": "primary"}
      ]
    }
  ]
}

Essential Information

Every alert should include:

• Status - Up/Down with emoji indicator
• Monitor name - Which service is affected
• Error details - HTTP code, error message
• Duration - How long it's been down
• Action link - Quick access to dashboard

Notification Settings

Configure Alert Types

Choose what triggers notifications:

• Down alerts - Always enable
• Recovery alerts - Recommended
• Degraded performance - Optional
• SSL expiry warnings - Recommended

Quiet Hours

Prevent non-critical alerts during off-hours:

Critical (service down): 24/7
Warning (slow response): 8 AM - 10 PM only
Info (minor issues): Business hours only

Using Slack Workflows

Automated Incident Response

Create Slack Workflow for incoming alerts:

1. Trigger: Message in #alerts-production
2. Action: Create thread
3. Action: Invite @oncall-team
4. Action: Post incident template

Escalation Workflow

If no response within 10 minutes:

1. Trigger: No reaction to alert message
2. Action: DM @oncall-primary
3. Action: Post in #escalations

Best Practices

Do

• Use threads for discussion
• React with emoji to acknowledge
• Pin active incidents
• Use @channel sparingly
• Archive resolved incidents

Don't

• Alert to #general
• Send test alerts to production channels
• Ignore alert fatigue signals
• Use unclear monitor names

Slack Integration Checklist

• Slack app or webhook created
• Connected to monitoring service
• Channel routing configured
• Message format verified
• Test alert sent and received
• Team notified of new alerts
• Escalation workflow set up

Troubleshooting

Alerts Not Arriving

1. Check webhook URL is correct
2. Verify channel exists and is public (or bot is invited)
3. Test webhook manually with curl
4. Check monitoring service logs

Rate Limiting

Slack has rate limits. If hitting them:

• Reduce alert frequency
• Use deduplication
• Consider summary alerts

Wrong Channel

If alerts go to wrong channel:

• Verify webhook is for correct channel
• Check channel routing in monitor settings
• Ensure correct integration is selected