Understanding Server Status Indicators

Server Scout uses a comprehensive status indication system to help you quickly assess the health of your server infrastructure. Understanding these indicators is crucial for effective monitoring and rapid incident response.

The Five Server States

Server Scout categorises each monitored server into one of five distinct states, each with its own colour-coded indicator:

Online (Green)

Your server is functioning normally when it appears with a green status badge. This indicates that Server Scout has received monitoring data within the last 15 seconds. An online status means your server is actively reporting metrics and responding to health checks as expected.

Warning (Amber/Orange)

When a server displays an amber warning status, it means no monitoring data has been received for 15-60 seconds. This intermediate state serves as an early warning that something might be amiss. Temporary network issues, high server load, or brief service interruptions often trigger this status.

Offline (Red)

A red offline status indicates that Server Scout hasn't received any data from your server for more than 60 seconds. This typically suggests a serious issue such as server downtime, network connectivity problems, or agent failure. Offline servers require immediate attention.

Paused (Grey)

The grey paused status appears when you've manually disabled monitoring for a server through the admin interface. This is useful during planned maintenance windows, server migrations, or when decommissioning systems. Paused servers don't generate alerts or affect fleet health calculations.

Initialising (Blue)

New servers display a blue initialising status immediately after being added to Server Scout. This state persists until the system receives its first successful check-in from the server's monitoring agent. Depending on your configuration, initialisation typically completes within 30-60 seconds.

How Status is Determined

Server Scout determines status by examining the timestamp of each server's last successful check-in. The system continuously compares this timestamp against the current time:

1. Calculate time difference: Server Scout subtracts the last check-in time from the current time
2. Apply status thresholds: The resulting duration determines which status category applies
3. Update indicators: Status badges refresh automatically as conditions change

This timestamp-based approach ensures accurate, real-time status reporting across your entire server fleet.

Understanding Status Badges

On your server dashboard, each monitored system displays a prominent status badge with both colour coding and text labels. These badges provide immediate visual feedback about server health:

• Green badges with "Online" text indicate healthy, responsive servers
• Amber badges showing "Warning" highlight servers requiring attention
• Red badges marked "Offline" signal critical issues needing urgent intervention
• Grey badges labelled "Paused" identify manually disabled monitoring
• Blue badges displaying "Initialising" show newly added servers pending first contact

The badges update dynamically without requiring page refreshes, ensuring you always see current status information.

Fleet Health Overview

The fleet health bar at the top of your dashboard provides an aggregated view of your entire server infrastructure. This horizontal bar displays:

• Segment colours corresponding to each status type
• Proportional sizing reflecting the count of servers in each state
• Quick counts showing exact numbers when hovering over segments

For example, if you're monitoring 20 servers with 15 online, 3 in warning state, 1 offline, and 1 paused, the fleet health bar will show green占ing 75% of the space, amber taking 15%, red representing 5%, and grey accounting for 5%.

Best Practices

Monitor your fleet health bar regularly throughout the day. A predominantly green bar indicates a healthy infrastructure, while increasing amber or red segments warrant investigation.

Consider setting up automated alerts based on status changes to ensure prompt response to developing issues. Remember that paused servers don't contribute to health calculations, so use this feature judiciously during maintenance windows.

Understanding these status indicators empowers you to maintain optimal server performance and respond swiftly to infrastructure challenges.