The public-facing Status Page is the final, white-labeled delivery layer of your monitoring stack. It translates complex server and application metrics into a clean, minimalist dashboard that customers and stakeholders can interpret at a glance.

This layout is fully responsive, supports a native Dark Mode toggle in the footer, and actively suppresses internal administrative configurations while maintaining high operational clarity.

1. Branded Header & Support Navigation

The top menu bar features your custom administrative brand styling and provides direct links to shield your customer service desk from redundant support queries:

• Brand Title: Displays your clean workspace identifier or custom company logo in the upper left corner.
• Website Link: A quick navigation shortcut allowing users to jump back to your primary application or business homepage.
• Contact Button: A prominent action button routing clients directly to your designated support desk, ticketing channel, or emergency email loop (mailto:).

2. Broad System Health Summary

Directly below the header, a high-visibility global health indicator gives users instantaneous validation of your platform's operational status:

• Global Health Banner: When all monitors are completely functional, the header broadcasts a clean "All services are Online" notice with a green confirmation mark (🟢). If a component degrades or falls offline, this card dynamically adjusts its alert message to keep users informed.
• Synchronized Heartbeat Timestamp: Displays the exact calendar date, time, and timezone of the most recent automated scan cycle.
• Manual Refresh Control: Users can click the circular refresh icon (🔄) next to the timestamp to force an instant client-side update of the status cards.

3. Rolling Aggregate Availability Vitals

Three high-impact cards calculate your environment's mathematical uptime history across staggered operational windows, helping prove long-term infrastructure stability:

• Last 24 Hours: Displays a high-resolution rolling uptime average over the past day, highlighting immediate service drops.
• Last 7 Days: Tracks average performance over the past week to showcase mid-term reliability.
• Last 30 Days: Compiles a comprehensive monthly availability rating, giving corporate enterprise clients clear visual proof that your platform is consistently meeting its Service Level Agreements (SLAs).

4. Granular 90-Day Component Timelines

The core of the interface breaks down your environment into individual monitoring tracks. Each component block maps out active status profiles over a trailing 90-day timeline:

Asset Profiling & Security Badges

• Component Metadata: Lists the customized name of the node stacked over its operational class (e.g., Website or Server).
• Security Indicators: Lock icons (🔒) and network icons (🌐) validate that the endpoint is running over an active, secure HTTPS connection layer.
• Uptime Percentage: The component's individual, absolute long-term performance rating (e.g., 100.00% uptime, 99.93% uptime).

Decoding the Timeline Color Bars

The timeline bar splits each day into vertical blocks. To help users differentiate network connection issues from local computational strains, the blocks utilize two distinct contextual legends:

5. Transparent Public Incident History Log

The Recent Incidents table acts as an open audit book, logging individual historical stability events clearly. Veyon balances internal security with customer transparency by sanitizing technical messages—keeping clients fully informed without exposing backend infrastructure vulnerabilities.

Logged Incident Visuals

• Component Association: Identifies the precise system node that experienced the anomaly (e.g., Seanergy Dev Server or Hexomm).
• Sanitized Root Cause Text: Translates errors into readable metrics. It accurately logs system resource caps for internal workers (e.g., Tcp Connections Incident - critical threshold sustained) or explicitly surfaces external client-side blocking issues (e.g., cURL error 28: Connection timed out after 10002 milliseconds) so your customers know exactly if a failure was caused by an internal code break or an external service provider outage.
• Resolution Banner: A green badge marks resolved issues, indicating exactly how long the disruption lasted (e.g., resolved (7m), resolved (38m)).
• Time Tracking: Displays the precise historical hours and minutes the issue occurred, giving clients the exact timestamps they need to cross-verify their own internal automation failures.