Pausing and Resuming Server Monitoring

When to Pause Server Monitoring

There are several scenarios where temporarily pausing monitoring for a server makes perfect sense. Whether you're performing planned maintenance, decommissioning a server, working with temporary environments, or investigating known issues where constant alerts would create unwanted noise, Server Scout's pause functionality gives you the control you need.

Pausing monitoring is particularly useful when you want to keep the server registered in your dashboard without the overhead of full metric collection or the distraction of alerts during planned downtime.

How to Pause a Server

Pausing monitoring for any server in your Server Scout dashboard is straightforward:

1. Navigate to your server dashboard and locate the server card you wish to pause
2. Click the three-dot menu (⋯) in the top-right corner of the server card
3. Select "Pause Monitoring" from the dropdown menu

The change takes effect immediately, and you'll notice the server card updates to reflect the new status.

What Happens When a Server Is Paused

When you pause monitoring for a server, several important changes occur:

Agent Behaviour Changes

The Server Scout agent switches to heartbeat-only mode. Instead of collecting and transmitting full metrics every 5 seconds, the agent sends a minimal check-in every 60 seconds. This lightweight heartbeat simply confirms the agent is still running and the server is reachable.

Visual Indicators

The server card in your dashboard displays a "Paused" status badge, making it immediately clear which servers are not under active monitoring. This visual indicator helps prevent confusion when reviewing your server fleet.

Alert Suspension

No alerts are triggered for paused servers, regardless of their actual system state. This prevents notification spam during maintenance windows or when you're already aware of issues being investigated.

Fleet Health Statistics

Paused servers do not contribute to your online/offline fleet health statistics. This ensures your overall infrastructure health metrics remain accurate and representative of servers that should be actively monitored.

Metric Collection

Historical metric collection is completely suspended. No CPU, memory, disk, network, or other performance data is gathered whilst the server remains paused. This reduces both storage overhead and processing requirements.

Resuming Server Monitoring

When you're ready to return a server to full monitoring, the process is equally simple:

1. Locate the paused server card (identifiable by its "Paused" status badge)
2. Click the three-dot menu (⋯) on the server card
3. Select "Resume Monitoring" from the dropdown menu

What Happens Upon Resume

The moment you resume monitoring, several processes kick in automatically:

• The agent immediately resumes full metric collection at 5-second intervals
• All collection tiers are refreshed to ensure comprehensive data gathering
• Alert monitoring becomes active again, with all configured thresholds back in effect
• The server returns to contributing to your fleet health statistics

Best Practices and Use Cases

Planned Maintenance Windows

Before performing system updates, reboots, or infrastructure changes, pause monitoring to avoid false alerts. Remember to resume monitoring once maintenance is complete to ensure continued oversight.

Server Decommissioning

When gradually retiring servers, pause monitoring to maintain a clean dashboard whilst keeping the server record for reference. This is particularly useful during phased migrations.

Temporary Environments

Development or testing servers that are frequently started and stopped benefit from paused monitoring during inactive periods, reducing alert noise without losing the ability to monitor when needed.

Issue Investigation

When you're already aware of server problems and actively investigating, pausing prevents alert fatigue whilst maintaining the heartbeat connection for when you're ready to resume full monitoring.

The pause and resume functionality in Server Scout provides the flexibility to maintain clean, relevant monitoring whilst accommodating the real-world complexities of server management.