Testing Notification Channels

Server Scout's notification system is only effective when your alerts actually reach you. Testing your notification channels ensures that critical alerts won't disappear into the void when you need them most.

The Test Channel Feature

Server Scout includes a built-in testing mechanism accessible from the Notifications settings page. This feature allows you to send a test notification to any configured channel without waiting for an actual alert condition to occur.

To access the test functionality:

1. Navigate to Settings > Notifications
2. Locate the channel you wish to test
3. Click the Test Channel button next to your configured notification method

Sending Test Notifications

The test system works with all supported notification channels:

• Dashboard notifications - Appear in your Server Scout interface
• Webhook integrations - Including Slack, Microsoft Teams, Discord, and custom endpoints
• Email notifications - Sent to your configured email addresses

When you initiate a test, Server Scout sends a sample alert containing realistic test data. The test notification mimics the format and content of actual alerts, including:

Alert: Test Notification
Server: test-server-01
Metric: CPU Usage
Value: 85%
Threshold: 80%
Status: Critical
Time: 2024-01-15 14:30:00 UTC

Verifying Test Delivery

Dashboard Notifications

For dashboard alerts, check the notification bell icon in your Server Scout interface. The test notification should appear immediately in your notifications list, marked clearly as a test message.

Webhook Endpoints

Webhook delivery verification depends on your endpoint type:

Slack/Teams/Discord: Check the designated channel for your test message. It should appear within seconds of sending.

Custom webhooks: Monitor your endpoint's logs or response handling to confirm the POST request arrived with the expected JSON payload.

Email Notifications

Check your email inbox, including spam folders. Test emails typically arrive within 1-2 minutes, depending on your mail server's processing time.

Troubleshooting Failed Tests

Webhook Issues

SSRF Protection Blocks: Many hosting providers block requests to private IP ranges (10.x.x.x, 172.16-31.x.x, 192.168.x.x) as a security measure. If your webhook endpoint uses internal network addresses, you may need to:

• Use a public-facing endpoint
• Configure your hosting provider's SSRF settings
• Implement a relay service for internal notifications

Invalid URLs: Verify your webhook URL is correctly formatted and accessible. Test it manually using curl:

curl -X POST -H "Content-Type: application/json" \
  -d '{"text":"Manual test"}' \
  https://your-webhook-url.com/endpoint

Email Delivery Problems

SMTP Configuration: Double-check your SMTP settings:

• Server hostname and port
• Authentication credentials
• Encryption method (TLS/SSL)

SSL/TLS Errors: If you encounter certificate errors, verify:

• Your SMTP server supports the configured encryption method
• Certificates are valid and not expired
• Your Server Scout instance can reach the SMTP server on the specified port

Common SMTP ports:

• 587 - STARTTLS (recommended)
• 465 - SSL/TLS
• 25 - Unencrypted (not recommended)

General Troubleshooting Steps

1. Check Server Scout logs for detailed error messages
2. Verify network connectivity from your Server Scout instance
3. Test with alternative channels to isolate the issue
4. Review firewall rules that might block outgoing connections

Best Practices for Channel Testing

Initial Configuration: Always test new notification channels immediately after setup. This confirms your configuration is correct before you rely on it for critical alerts.

Periodic Testing: Schedule regular tests of your notification channels—monthly testing catches issues before they impact your monitoring:

• Email server changes or credential expiry
• Webhook endpoint modifications
• Team channel reorganisations
• Network configuration changes

Multiple Channels: Configure and test multiple notification methods for redundancy. If one channel fails, you'll still receive critical alerts through backup channels.

Testing your notification channels is a small investment of time that prevents much larger problems. When that critical server alert fires at 3 AM, you'll be grateful you took the time to verify your notifications work properly.