Slack Integration: Get Synthetic Monitoring Alerts in Slack

Connect supaguard to Slack to receive instant notifications when your synthetic checks fail or recover. This guide covers setup, configuration, and best practices for effective Slack alerting.

Why Slack for Monitoring Alerts?

Slack is where your team already works. By sending supaguard alerts to Slack, you:

• Get instant visibility when checks fail
• Enable quick team coordination during incidents
• Keep a searchable history of all alerts
• Avoid the noise of email notifications

Quick Setup

Step 1: Create a Slack Incoming Webhook

1. Go to Slack API: Incoming Webhooks
2. Click Create your Slack app (or select an existing app)
3. Choose From scratch and name it "supaguard Alerts"
4. Select your workspace
5. Navigate to Incoming Webhooks in the sidebar
6. Toggle Activate Incoming Webhooks to On
7. Click Add New Webhook to Workspace
8. Select the channel for alerts (e.g., #alerts or #ops-monitoring)
9. Copy the webhook URL

Your webhook URL looks like:

https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Step 2: Add the Webhook to supaguard

1. Log in to your supaguard dashboard
2. Go to Settings → Communications
3. Click Add Channel
4. Select Slack
5. Paste your webhook URL
6. Give it a name (e.g., "Ops Alerts Channel")
7. Click Save

Step 3: Test the Integration

1. In the channel settings, click Send Test
2. Verify the message appears in your Slack channel
3. If it works, you're all set!

Alert Message Format

supaguard sends rich Slack messages with:

🔴 Check Failed: Homepage Load Test

Status: CRITICAL
URL: https://example.com
Location: San Francisco
Duration: 5,234ms
Error: Timeout waiting for element

[View Details] [View Trace]

Message includes:

• Check name and status
• Failure classification (Critical, Degraded)
• Target URL
• Location where the check ran
• Execution duration
• Error message
• Quick links to debug

Best Practices

Create Dedicated Alert Channels

Don't send alerts to a busy general channel. Create dedicated channels:

• #alerts-critical — Only Critical failures (PagerDuty-worthy)
• #alerts-warnings — Degraded performance issues
• #ops-monitoring — All monitoring activity

Use Channel Separation by Severity

Configure multiple Slack channels in supaguard:

Configure Alert Policies

In Alert Policies, assign different Slack channels based on severity:

1. Create a policy for critical alerts
2. Assign your #alerts-critical channel
3. Create a separate policy for warnings
4. Assign your #alerts-warnings channel

Set Up Escalation Flows

Combine Slack with other channels:

1. Immediate: Slack notification to #alerts
2. After 15 minutes: PagerDuty page if unresolved
3. Recovery: Slack notification when fixed

Slack Enterprise Grid

For Slack Enterprise Grid workspaces:

1. Ensure the supaguard app is approved in your org
2. Create webhooks in the specific workspace (not org-level)
3. Follow the standard setup process

Contact your Slack admin if app installation is restricted.

Troubleshooting

Alerts Not Appearing

1. Verify webhook URL — Test it with curl:

   curl -X POST -H 'Content-type: application/json' \
     --data '{"text":"Test from terminal"}' \
     YOUR_WEBHOOK_URL

2. Check channel permissions — Ensure the webhook has access to post

3. Verify supaguard settings — Confirm the channel is enabled and assigned to checks

Messages Look Broken

Ensure you're using the Incoming Webhook integration, not a custom bot. supaguard sends Slack Block Kit formatted messages that require the webhook integration.

Rate Limiting

Slack has rate limits (~1 message per second). If you have many checks failing simultaneously:

• supaguard batches notifications when possible
• Consider consolidating checks if you see missing alerts

Advanced: Custom Webhook Payloads

For advanced customization, use supaguard's generic Webhook integration instead of the native Slack integration. This lets you:

• Customize the message format completely
• Add custom fields
• Integrate with Slack workflows

See our Webhooks Integration Guide for details.

Security Considerations

• Keep webhook URLs secret — Anyone with the URL can post to your channel
• Use private channels for sensitive alerts
• Rotate webhooks periodically if team members leave
• Don't log webhook URLs in version control

Related Resources

• Configuring Alerts — Set up alert policies
• PagerDuty Integration — For critical on-call alerts
• Communications Overview — All notification channels