While the main Overview provides a high-level snapshot, the Resources tab acts as your primary terminal inspection interface. It surfaces process lists, active background utilities, security patches, and rolling 7-day performance maps.

Resource Menu

Directly beneath the sub-navigation tabs, you will see a local menu bar for detailed charts of each server resource:

• Metric Links (CPU, Memory, Disk, Network, I/O Wait): Clicking any individual link shows the detailed view of server resource, to focus exclusively on that single hardware element's deep historical charts and detail.
• Services: Jumps directly to the daemon management matrix.

1. System Information Profile

Similar to Overview page, Resources page also shows cards with details captured 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:

3. Core Services Audit

The Services panel functions as an automated supervisor for background systems running on your host operating system. It explicitly tracks how many total services are active (e.g., 14/15 running). 

Each configured service is listed alongside a live status color indicator:

• 🟢 Green: The service daemon is actively running and processing tasks normally (e.g., mysql, apache2, sshd, or multi-version PHP layers like php8.3-fpm).
• 🔴 Red: The service has stopped, crashed, or been terminated manually (e.g., named). This flag alerts you immediately if a critical database layer or web proxy falls over silently.

4. Security Vitals Hub

The Security panel runs a continuous diagnostic check on standard threat protection, patch states, and package managers:

• Failed logins (24h): Aggregates SSH or system authentication failures over the past day. Sudden numeric spikes indicate an active brute-force attempt, alerting you to adjust firewall rules.
• Reboot required: Displays an explicit Yes or No tag indicating whether a recently installed kernel or system update demands a system restart to complete configuration.
• Updates pending / Security updates: Quantifies standard packages and critical security updates waiting in your package manager queue (e.g., apt or yum), ensuring you stay on top of server hardening.

5. Top Processes (by CPU)

This dynamic execution table mimics an active system monitor utility, profiling the top ten application threads consuming the most processor power or system memory. It updates automatically in the background (e.g., 55 seconds ago).

6. Long-Term Rolling Performance & Incident History

Uptime Status — Last 7 Days

A high-level visual health block matrix mapping out your infrastructure stability across the past calendar week.

• Each day (Mon–Sun) is represented by a solid block.
• A clean green row validates sustained baseline operations, contributing to your aggregate historical uptime rating (e.g., 99.99%).

Triage Summary Cards

The page closes with condensed activity feeds to check immediate context without leaving the screen:

• Recent Checks: Displays the last 10 continuous data transmissions received from the agent script daemon, listing the response state and execution speeds (e.g., HTTP 200 • 763ms).
• Recent Incidents: Logs the last 5 hardware metric violations, highlighting resolved durations (e.g., resolved (6m)) to quickly assess historical bottleneck trends.

CPU Analytics & Intelligent Baselining

The CPU sub-menu provides a deep granular analysis of your server's processing core utilization. Beyond simple real-time charting, Veyon employs machine learning to map out normal operational baselines and auto-calculate intelligent alert thresholds for your specific workload.

1. The Interactive CPU Utilization Graph

The primary timeline chart maps out aggregate CPU utilization percentage (Y-axis) against the hours of the day (X-axis). The chart plots three key metrics simultaneously:

• 🔵 Value (Solid Blue Line): The active, rolling CPU usage percentage reported by the background monitor agent script.
• 🩶 Threshold (Grey Dashed Line): The warning line (e.g., 85.0%). If the blue line sustains a position above this limit, an incident is evaluated.
• 🔴 Critical (Red Dashed Line): The absolute maximum system threshold capacity (100.0%), indicating total processor saturation.

Pro Tip: Hover your mouse anywhere along the timeline graph to open a live tooltip inspection box, showing the exact timestamped values for the workload, warning thresholds, and critical limits at that specific second.

2. Resource Statistics & Learned Baselines

The Statistics panel splits your core processing data into two core areas: high-level performance boundaries and algorithmic behavior metrics.

Core Performance Bounds

Intelligent Machine Learning Metrics

• Samples in range: The total number of individual data records used to compute the analytics for the window (e.g., 1,303 60-second samples).
• Baseline (learned): Veyon tracks your server's long-term behavior to calculate a standard deviation model (e.g., 29.17% ± 25.56%). This represents your infrastructure's true "normal operational comfort zone."
• Threshold (alert): An auto-calculated alert margin generated dynamically by analyzing your learned baseline. This ensures you only get alerted when usage breaks away from typical resource patterns, significantly reducing false alarms.
• Critical: The hard ceiling threshold that triggers an immediate high-priority alert when reached.

3. Localized CPU Incidents Feed

The bottom of the view isolates historical alert events tied exclusively to processor constraints.

When a processor bottleneck occurs, the card tracks:

• Incident Label: Clearly flagged as a CPU incident.
• Peak Breach Load: The highest resource volume reached during the event (e.g., 100.00%).
• Resolution State: Displays a red warning icon for live events, or a green confirmation checkmark once resolved, showing the exact time it took the server to cool down (e.g., resolved (4m)).
• Root Trigger Text: The underlying condition logged (e.g., critical threshold sustained), alongside the exact execution timestamp when the alarm sequence initially fired.

Memory Analytics & Allocation Tracking

The Memory sub-menu delivers an exact analysis of your server's Random Access Memory (RAM) utilization. Tracking memory footprints is critical for identifying application memory leaks, optimization opportunities for database caching, and preventing unexpected system instability caused by Out-Of-Memory (OOM) kernel events.

1. The Interactive Memory Utilization Graph

The timeline chart plots your server's aggregate RAM occupancy percentage (Y-axis) relative to the time of day (X-axis). The visualization tracks three concurrent parameters:

• 🟢 Value (Solid Green Line): The active, rolling memory usage percentage reported by the local monitor agent.
• 🩶 Threshold (Grey Dashed Line): The alert warning boundary (e.g., 42.2%). If memory consumption surges and remains above this algorithmic mark, the system begins auditing for an incident.
• 🔴 Critical (Red Dashed Line): The absolute maximum safety limit defined for the machine (98.0%), signaling total memory exhaustion.

Pro Tip: Hover your cursor along the data paths to display a live tracking tool-tip box, showing the exact timestamped values for active usage, warning limits, and critical ceilings at that precise minute.

2. Memory Resource Statistics & Learned Baselines

The Statistics panel tracks data boundaries alongside Veyon's intelligent workflow baselines to provide deep context on your execution environment.

Core Allocation Boundaries

Algorithmic Behavior Metrics

• Samples in range: The net quantity of data packets processed during the active window (e.g., 1,322 60-second samples).
• Baseline (learned): The machine-learning model's calculated standard operational footprint for your memory (e.g., 30.70% ± 0.80%). A tight margin indicates stable, highly predictable software memory usage.
• Threshold (alert): The auto-calculated warning trigger (e.g., 42.16%) adapted specifically to your server's historical footprint, preventing generic alert fatigue.
• Critical: The hard ceiling threshold (98.00%) that triggers an immediate high-priority notification to prevent application crashes.

3. Localized Memory Incidents Feed

The lower section isolates history logs down exclusively to memory threshold breaches.

• When your environment is operating smoothly within its calculated parameters, this panel displays a clean "No incidents in this range" confirmation status.

• If an application thread or database query leaks memory and crosses your auto-calculated thresholds, an emergency event entry will log the peak allocation breach, the exact start timestamp, and total resolution time needed to clear the space.

Disk Space & Capacity Auditing

The Disk sub-menu tracks the storage volume utilization of your server's root and attached filesystems. Unmonitored disk accumulation is a critical threat to server stability; if a disk fills up completely, databases will fail to write new rows, log rotations will break, and the operating system can lock up entirely.

1. The Interactive Disk Utilization Graph

The timeline chart records your absolute disk storage occupancy percentage (Y-axis) mapped across your selected timeframe (X-axis). Because server storage generally grows linearly rather than fluctuating rapidly like CPU or RAM, this graph is crucial for visualizing long-term storage consumption trends:

• 🟧 Value (Solid Orange Line): The active, rolling storage capacity percentage currently utilized across the filesystem.
• 🩶 Threshold (Grey Dashed Line): The alert warning boundary (e.g., 80.0%). If storage crosses this mark, Veyon flags a warning to allow your team to clear logs or expand volumes before an emergency occurs.
• 🔴 Critical (Red Dashed Line): The absolute maximum safety ceiling defined for the volume (95.0%), signaling imminent storage exhaustion.

Pro Tip: Hover your mouse along the timeline to open the contextual tooltip box, displaying the exact historical usage percentage, warning boundaries, and critical limits recorded at that precise timestamp.

2. Disk Resource Statistics & Capacity Baselines

The Statistics panel provides hard resource boundaries alongside Veyon's baseline learning algorithms to help you forecast storage depletion.

Core Capacity Boundaries

Capacity Management Metrics

• Samples in range: The total number of individual 60-second storage checkpoints analyzed (e.g., 1,347 60-second samples).
• Baseline (learned): The machine-learning model's structural evaluation of your standard usage footprint (e.g., 47.00% ± 0.00%). A stable baseline with zero standard deviation suggests regular, predictable disk usage without rapid data growth.
• Threshold (alert): The auto-calculated alert margin (e.g., 80.00%) matched to your server's filesystem size and historical data to prevent premature warnings.
• Critical: The maximum allowable ceiling (95.00%) that triggers an immediate, high-priority alert to protect your data integrity.

3. Localized Disk Incidents Feed

The lower section isolates system alerts specifically triggered by storage limitations.

• When your environment maintains plenty of free storage blocks, this section displays a clean "No incidents in this range" safety status.
• If a runaway application log file, rapid user uploads, or an unmanaged database backup breaches your warning or critical limits, an emergency ticket will drop here, logging the peak capacity breach, the exact date, and the elapsed time before storage space was successfully reclaimed.

Network Throughput & Bandwidth Monitoring

The Network sub-menu tracks the total volume of data flowing into and out of your server’s network interfaces. Monitoring network throughput is essential for identifying unexpected traffic surges, tracking API payload consumer patterns, diagnosing data sync bottlenecks, and catching potential security anomalies (such as DDoS traffic spikes or unauthorized data extraction) before your network pipe saturates.

1. The Interactive Network Throughput Graph

The timeline chart records your server's combined inbound and outbound network data transfer speeds, mapping throughput velocity (Y-axis) against the hours of the day (X-axis).

• 🟣 Value (Solid Purple Line): The rolling, real-time data throughput rate calculated by the background monitoring agent. The metrics dynamically scale across standard data units, adjusting automatically between Kbps (Kilobits per second) and Mbps (Megabits per second) based on volume.
• 🩶 Threshold (Grey Dashed Line): The warning alert boundary (e.g., 1.00 Mbps). If your server's sustained traffic climbs and sits above this line, the system flags a potential anomaly.

Pro Tip: Hover your mouse anywhere along the purple data line to reveal a live metadata tooltip box, displaying the exact timestamped traffic volume and active alert threshold configuration down to the minute.

2. Network Resource Statistics & Traffic Baselines

The Statistics panel breaks down traffic velocity limits and isolates structural network behaviors calculated by Veyon's baseline machine-learning algorithms.

Core Throughput Boundaries

Algorithmic Traffic Metrics

• Samples in range: The total number of individual 60-second network data checks evaluated during the active window (e.g., 1,352 60-second samples).
• Baseline (learned): The statistical "normal behavior window" calculated automatically for your network interface traffic profile (e.g., 36.1 Kbps ± 773.6 Kbps).
• Threshold (alert): The auto-calculated alert margin (e.g., 1.00 Mbps). Veyon dynamically places this line above your standard operational baseline deviation to shield you from false alarms caused by expected micro-bursts.
• Critical: Displays — (None Defined). Because network connections are inherently elastic and rarely suffer from catastrophic physical exhaustion errors like disk or RAM limits, Veyon relies on a flexible warning threshold model rather than a rigid critical hard ceiling.

3. Localized Network Incidents Feed

The lower section isolates system alert logs down exclusively to bandwidth or network threshold violations.

• When your network layer is transferring standard daily volumes cleanly within its normal parameters, this panel displays a clean "No incidents in this range" status card.
• If a traffic flash-mob, runaway script loop, or external database dump breaches your auto-calculated thresholds, a specialized network incident row will immediately drop here to document the peak traffic breach speed, initial trigger timestamp, and total duration of the event.

I/O Wait Analytics & Storage Bottleneck Tracking

The I/O Wait (Input/Output Wait) sub-menu tracks a critical but frequently overlooked system health metric: the percentage of time your CPU sits idle while waiting for disk storage read/write operations or network storage requests to complete.

Even if your raw CPU usage looks low, a high I/O Wait percentage means your applications are freezing or lagging because your storage drives cannot process data requests fast enough. This is a vital diagnostic screen for identifying unoptimized database queries, slow SSD/HDD hardware degradation, or heavy file serialization bottlenecks.

1. The Interactive I/O Wait Graph

The timeline chart records your host machine's aggregate I/O wait percentage (Y-axis) plotted against your selected time window (X-axis). The visual interface displays three concurrent tracking paths:

•  🟪 Value (Solid Pink Line): The active, rolling percentage of CPU cycles spent waiting on storage operations, reported in real-time by the monitor agent.
• 🩶 Threshold (Grey Dashed Line): The warning alert boundary (e.g., 20.0%). If sustained disk operations push the pink line above this line, Veyon flags a potential storage slowdown.
• 🔴 Critical (Red Dashed Line): The absolute maximum safety ceiling defined for the server (80.0%), signaling severe storage queue bottlenecks that will degrade application performance.

Pro Tip: Hover your cursor over any point along the timeline to open the live metadata tooltip box, revealing the exact timestamped I/O Wait values, warning limits, and critical ceilings down to the minute.

2. I/O Wait Statistics & Storage Baselines

The Statistics panel provides high-level storage processing boundaries combined with Veyon's baseline machine-learning calculations to help you isolate irregular storage spikes from normal background operations.

Core I/O Boundaries

Intelligent Disk Performance Metrics

• Samples in range: The total number of individual 60-second storage checkpoints analyzed during the active window (e.g., 1,353 60-second samples).
• Baseline (learned): The machine-learning model's structural evaluation of your standard storage execution footprint (e.g., 0.08% ± 0.26%). This represents your drive array's true normal operational comfort zone.
• Threshold (alert): The auto-calculated alert margin (e.g., 20.00%). Veyon dynamically places this warning trigger above your standard disk baselines to prevent alert fatigue from normal, short-lived storage tasks.
• Critical: The hard maximum ceiling (80.00%) that triggers an immediate, high-priority notification to protect your services from locking up due to drive starvation.

3. Localized I/O Wait Incidents Feed

The lower section isolates system alerts specifically triggered by disk read/write delays.

• When your storage array handles data blocks cleanly within its normal parameters, this section displays a clean "No incidents in this range" status card.
• If a heavy application bottleneck or disk traffic overload breaches your warning or critical limits, an emergency ticket will drop here, logging the peak latency breach, the exact date, and the elapsed time before the storage queue cleared.

Background Services & Daemon Management

The Services sub-menu functions as a live process supervisor directly inside the Veyon dashboard. Instead of merely checking if the global operating system is powered on, this view provides deep visibility into the distinct software daemons handling your applications (such as web servers, database clusters, firewalls, and cron schedulers).

This interface allows you to isolate service-level crashes, audit individual daemon uptimes, and control which background applications trigger active paging notifications.

1. Global Service Metrics & Time Filters

At the top right of the resources view, you can use the localized time window toggle (24h, 7d, 30d) to scale your historical health reports. Directly below, four metric cards track aggregate software stability over that window:

• Services monitored: The net number of daemon components currently integrated into Veyon's inspection tracker (e.g., 15).
• Running: The quantity of background processes actively executing and healthy (e.g., 14).
• Stopped: The count of critical application daemons that are currently dead, terminated, or failed to start (e.g., 1).
• Avg uptime: The combined historical reliability score of all tracked services during the selected time boundary (e.g., 93.33%).

2. The Services Management Matrix

The core table maps out the real-time operational signature of your background infrastructure:

3. Advanced Operational Toggles

Direct Monitoring Control (The Monitor Checkbox)

Veyon provides complete flexibility over system alerting rules. By checking or unchecking the box in the Monitor column, you can opt out of tracking specific background software. For instance, if you intentionally take a caching module or a localized web proxy offline for re-indexing, unchecking its box prevents Veyon from generating false infrastructure incidents while keeping your other server logs active.

Strict Mode Toggle

Located at the top right of the table header, the Strict mode switch (defaulted to OFF) controls how intensely service outages impact your overall infrastructure health score:

• Strict Mode OFF: Individual service drops (like a stopped named daemon) are highlighted within this panel, but they do not automatically trigger a high-priority, server-wide "Unavailable" incident if the core server port remains reachable.
• Strict Mode ON: Tightens security protocols. The moment any single enabled service daemon experiences a failure or enters a stopped state, Veyon instantly escalates the issue, flagging the entire server node as degraded and routing immediate emergency alerts to your configured notification channels.