Once the Veyon agent is deployed and communication is established, clicking a server's name in the directory unlocks a comprehensive, internal resource-monitoring matrix.


Header Controls & Tab Navigation


  • Live Indicator Status: The top right features two tracking tags. The Live pill indicates the daemon is currently streaming active data, while the Online pill validates that the target port is responding.
  • Context Menus: Use the action icon (...) for options to modify server endpoints, see incidents, install Veyon Agent, pause/resume monitoring, and delete this server from monitoring. The date filter dropdown (defaulted to Today) updates all resource graphs and event logs for specific historical audits by Today, Yesterday, Last 7 Days, Last 30 Days, etc.
  • Sub-Navigation Tabs: Switch views between Overview (core vitals), Resources (deep-dive metrics), Checks (data push history), and Incidents (triggered hardware alarms).

1. System Information Profile

The leftmost card captures the host machine's foundational software environment and networking signature:

  • OS & Kernel: Identifies the precise operating system distribution (e.g., Ubuntu 22.04.5 LTS).
  • Hardware Specs: Displays the number of available CPU Cores, along with resource fraction bars mapping active usage against capacity for Total RAM and Disk storage.
  • System Uptime: Tracks how long the host hardware itself has been powered on and running continuously without a reboot (e.g., 2d 16h 8m).
  • Network Binding: Lists both the public/private IPv4 and IPv6 addresses allocated to the system node.
  • Services: Tracks the exact number of internal daemon processes (e.g., Web servers, caches, databases) actively hooked into Veyon monitoring.

2. Real-Time Resource Telemetry Cards

These dynamic health tiles visualize live computing thresholds, complete with mini sparkline charts tracking localized behavior patterns over the last few minutes:


Telemetry Card

Metric Tracked

Target State

CPU

The current processing load across all aggregate cores as a percentage.

Healthy / Critical

RAM

Active system memory allocation currently occupied by running software layers.

Healthy / Critical

DISK

Total storage utilization across the root partition, paired with a progress bar.

Healthy / Critical

NETWORK

Combined live inbound and outbound network data throughput bandwidth (e.g., 114.3 Kbps).

Live

I/O WAIT

The percentage of time the CPU sits idle waiting for disk read/write storage tasks to complete. High spikes indicate storage bottlenecks.

Healthy / Critical

CPU TEMPERATURE

Real-time thermal sensor outputs from the physical processor housing. Shows N/A on virtualization platforms if hardware sensors are abstract.

Healthy / Critical

 

3. Execution History & Activity Analytics

The midsection measures performance reliability over the duration of your selected calendar window:


  • Uptime Percentage: Your machine's absolute network availability baseline (e.g., 100.00%).
  • Report Age Card: Measures data freshness by showing the duration since the last script package drop (e.g., 1s) alongside the total quantity of checks completed.
  • Incidents Count: Accumulates the total volume of resource threshold violations captured during the timeframe.
  • Historical Activity Chart: An interactive line graph plotting cluster stability or hardware event markers over a 24-hour timeline.

4. Direct Activity Triage Logs (Bottom Section)

The Checks Feed

A scrolling, real-time confirmation log tracking the health of individual agent heartbeats. Rather than evaluating HTTP response strings, it records:

  • Status (200): Confirms a structurally complete data payload was received, if fails then it gives status code accordingly.
  • Report Age (1s): Validates that the transmission latency between the agent executing the script and Veyon receiving it is immediate.
  • Timestamp: The exact execution time of the check execution block.








The Incidents Feed

An event framework logging hardware threshold violations. Unlike generic pings, Veyon tracks deep internal states:

  • Specific Alert Categorization: Differentiates the exact system bottleneck causing an alarm, labeling instances clearly as a Load Avg Incident, CPU Incident, or TCP Connections Incident.
  • Sustained Log Metrics: Outlines the precise metric that breached safety margins (e.g., critical threshold sustained - 100.00% or sustained - 281.00 TCP connections), complete with clear start and resolution times to streamline root-cause forensic debugging.