Setting Up Server Offline Alerts

How Server Scout Detects Offline Servers

Server Scout continuously monitors your servers by expecting regular data transmissions from the monitoring agent. A server is considered offline when no data has been received for 60 seconds or more. Since agents send data at 5-second intervals by default, this means approximately 12 consecutive missed check-ins before triggering an offline alert.

Before reaching the fully offline state, servers enter a warning period when no data has been received for 15-60 seconds. This warning state helps distinguish between temporary network hiccups and genuine connectivity issues.

Default Offline Alert Configuration

When you add a new server to Server Scout, an offline alert condition is automatically created with sensible defaults. This ensures you'll be notified immediately if your server stops communicating, without requiring any additional configuration.

The default settings include:

• Trigger threshold: 60 seconds of no data
• Warning threshold: 15 seconds of no data
• Notification channels: Your account's default notification settings
• Automatic activation: The alert is enabled immediately

Customising Offline Alert Settings

You can fine-tune offline alerts to match your specific monitoring requirements and reduce false positives.

Adjusting the Sustain Period

The sustain period determines how long a server must be offline before triggering an alert:

1. Navigate to your server's alert configuration page
2. Select the offline alert condition
3. Adjust the Sustain Period field (minimum 60 seconds)
4. Save your changes

For servers with occasional connectivity issues, consider increasing the sustain period to 120-180 seconds to prevent unnecessary alerts.

Configuring Cooldown Periods

Cooldown periods prevent alert spam when servers frequently go offline and come back online:

1. Access the offline alert settings
2. Set the Cooldown Period (recommended: 300-600 seconds)
3. Apply the configuration

During the cooldown period, no new offline alerts will be sent for that server, even if it goes offline again.

Setting Notification Channels

Configure where offline alerts are sent:

# Example notification channels:
- Email notifications
- Slack integration
- Webhook endpoints
- SMS alerts (if configured)

You can specify different notification channels for offline alerts compared to other alert types, ensuring critical connectivity issues reach the right people immediately.

Common Causes of Offline Status

Understanding why servers go offline helps with faster troubleshooting:

Server Hardware Issues

• Physical server failure
• Power outages
• Hardware component failures

Network Connectivity Problems

• Internet connection outages
• Router or switch failures
• ISP-related issues

Agent-Related Issues

• Monitoring agent crashes
• Service stopped unexpectedly
• Insufficient system resources

Security Changes

• Firewall rule modifications blocking outbound connections
• Network security policy updates
• Port blocking at router level

System Administration

• Planned maintenance without pausing monitoring
• Server reboots taking longer than expected
• Service restarts affecting the agent

Paused vs Offline Servers

It's important to distinguish between paused and offline servers:

Paused Servers: When you manually pause monitoring for a server (during maintenance, for example), offline alerts are automatically suppressed. The server won't trigger offline notifications regardless of its actual status.

Offline Servers: These have genuinely stopped communicating with Server Scout unexpectedly and will trigger alerts according to your configured settings.

Always remember to unpause servers after completing maintenance to resume normal monitoring.

Data Recovery After Outages

One of Server Scout's valuable features is data spooling during outages. When a server comes back online after being offline, the monitoring agent automatically replays any historical data that was collected locally during the outage period.

This means you won't lose monitoring data during temporary connectivity issues, and you'll have a complete picture of what happened on your server during the offline period once connectivity is restored.

The agent intelligently queues data locally and transmits it in chronological order when communication with Server Scout resumes, ensuring your monitoring graphs and historical data remain accurate and complete.