Integrating Server Scout with Slack, Teams, and Discord

Overview

Server Scout's webhook notifications make it easy to integrate alert monitoring into your team's existing communication workflows. This guide covers setting up alert notifications with Slack, Microsoft Teams, and Discord, ensuring your team stays informed when server issues arise.

All three platforms receive colour-coded alerts: green for resolved issues, orange for warnings, and red for critical alerts. Each message includes the server name, affected metric, current value, and threshold that triggered the alert.

Slack Integration

Setting Up the Webhook

1. In your Slack workspace, navigate to Settings & administration > Manage apps
2. Search for "Incoming Webhooks" and add it to your workspace
3. Choose the channel where alerts should be posted (we recommend creating a dedicated #server-alerts channel)
4. Copy the generated webhook URL

Configuring Server Scout

1. Log into your Server Scout dashboard at app.serverscout.ie
2. Go to Settings > Notification Channels
3. Click Add Channel and select Webhook
4. Paste your Slack webhook URL
5. Name the channel (e.g., "Slack Alerts")
6. Use the Test Channel feature to verify the integration

Server Scout's payload format is natively Slack-compatible, so alerts will appear with proper formatting and colour coding immediately.

Microsoft Teams Integration

Creating the Webhook

Microsoft Teams offers two webhook options:

Option 1: Workflows (Recommended)

1. In your Teams channel, click the ... menu and select Workflows
2. Search for "Post to a channel when a webhook request is received"
3. Configure the workflow and copy the generated URL

Option 2: Incoming Webhook Connector

1. In your Teams channel, click ... > Connectors
2. Find "Incoming Webhook" and click Configure
3. Name your webhook and copy the URL

Adding to Server Scout

Follow the same steps as Slack configuration, pasting your Teams webhook URL instead. Teams connectors that accept Slack-compatible payloads will properly format Server Scout alerts with colour coding and structured information.

Discord Integration

Setting Up Discord Webhooks

1. Open your Discord server and navigate to the target channel
2. Click the gear icon (Channel Settings)
3. Select Integrations > Webhooks
4. Click New Webhook
5. Name your webhook (e.g., "Server Scout Alerts")
6. Copy the webhook URL
7. Important: Append /slack to the end of the URL

Configuration in Server Scout

Add the Discord webhook URL (with /slack suffix) to Server Scout following the same process as other platforms. The /slack suffix tells Discord to accept Slack-compatible payloads, ensuring proper formatting.

Testing Your Integration

After configuring any platform:

1. Use Server Scout's Test Channel feature in notification settings
2. Verify the test message appears in your chosen channel
3. Check that formatting and colours display correctly
4. Confirm the message contains all expected information

Alert Message Format

Regardless of platform, Server Scout alerts include:

• Server identification: Clear server name/hostname
• Metric details: Which metric triggered the alert (CPU, memory, disk space, etc.)
• Current value: The actual measured value
• Threshold: The limit that was exceeded
• Severity colour: Visual indication of alert importance
• Timestamp: When the alert was triggered

Troubleshooting Common Issues

Webhook URL Problems

• Expired URLs: Regenerate the webhook if messages stop appearing
• Permission changes: Ensure the webhook still has channel access
• Incorrect format: Verify Discord URLs include the /slack suffix

SSRF Protection

Server Scout's security features may block webhooks pointing to private IP addresses. If your chat platform uses internal URLs, contact support for assistance with SSRF validation configuration.

Missing Messages

• Check that notification rules are properly configured to route alerts to your webhook channel
• Verify the webhook URL hasn't changed in your chat platform settings
• Test the integration again using Server Scout's built-in testing feature

Best Practices

Channel Organisation

Create dedicated alert channels rather than posting to general discussion channels. This prevents alert fatigue and ensures important notifications aren't missed amongst regular conversation.

Alert Routing Strategy

Configure your notification rules thoughtfully:

• Send critical alerts to high-visibility channels where immediate action is expected
• Route warning alerts to monitoring channels checked regularly but not requiring instant response
• Consider separate channels for different server groups or environments (production vs. staging)

Team Coordination

Establish clear procedures for acknowledging and responding to alerts within your team communication platform, ensuring accountability and preventing duplicate responses to the same issue.