Servers

The Servers resource provides a consolidated view of every server reporting metrics within a specific environment. Each server is displayed as a card, allowing you to quickly assess key information at a glance and then drill into detailed performance graphs for in-depth analysis.

Navigation: Access Servers via the sidebar under the “Servers” section.

---

1. Servers Index

On the Servers index, each server in the selected environment appears as an individual card. Cards are sorted alphabetically by server name (or by a default order defined in your environment settings). Scroll or paginate as needed to locate a specific server.

1.1 Server Cards

Each server card displays the following fields:

• Server Name
  The unique identifier or hostname for this server (e.g., web-01, db-primary, worker-03).

• Operating System
  The OS distribution and version (e.g., Ubuntu 22.04, Amazon Linux 2).

• Laravel Version
  The version of Laravel running on this server (e.g., Laravel 10.x).

• PHP Version
  The PHP runtime version (e.g., PHP 8.1.2).

• CPU Usage
  The current CPU utilization percentage (e.g., 45%).

• Memory Usage
  The current memory utilization (e.g., 3.2 GB / 8 GB).

• Disk Usage
  The current disk utilization (e.g., 120 GB / 200 GB).

Tip: High CPU, memory, or disk usage on a card indicates potential resource pressure. Click the card to investigate historical trends and diagnose root causes.

1.2 Card Interactivity

• Clickable Cards
  • Clicking any server card navigates to that server’s Server Details page, where you can examine time-based performance metrics in greater depth.
• Hover States & Tooltips
  • Hovering over usage metrics (CPU, Memory, Disk) may reveal additional details, such as exact percentages or swap usage (if applicable).
• Color Coding
  • Usage values may be color-coded to indicate healthy (green), warning (orange), or critical (red) levels, allowing you to spot at-a-glance issues.

---

2. Server Details

Clicking a server card opens the Server Details page for that specific host. This view is divided into two main sections:

1. Server Summary Card
2. Performance Trends Graph

2.1 Server Summary Card

At the top of the Server Details page, a summary card displays the same set of fields that appeared on the index card:

• Server Name
• Operating System
• Laravel Version
• PHP Version
• CPU Usage (Current)
• Memory Usage (Current)
• Disk Usage (Current)

This card provides an immediate snapshot of the server’s identity and its real-time resource utilization.

Tip: If you notice any of the “Current” usage values in a warning or critical color, scroll down to the Performance Trends graph to determine whether this is a transient spike or part of a sustained trend.

2.2 Performance Trends Graph

Below the summary card, Laritor displays a line graph showing historical resource usage for CPU, Memory, and Disk over a selectable timeframe. Each metric is represented by a distinct colored line, making it easy to compare trends side by side.

2.2.1 Metrics Displayed

• CPU (Percentage)

  • Percentage of total CPU capacity used over time.

• Memory (Gigabytes)

  • Total memory consumed (e.g., “Used GB”) plotted against total available memory, expressed in GB.

• Disk (Gigabytes)

  • Total disk space used (e.g., “Used GB”) plotted against total disk capacity, expressed in GB.

2.2.2 Timeframe Selector

Above the graph, a Timeframe Selector allows you to choose one of the following spans:

• 1 Hour
• 3 Hours
• 6 Hours
• 12 Hours
• 24 Hours
• 1 Week
• 2 Weeks
• 30 Days

Selecting a timeframe updates the graph to show data points within that window. By default, the graph opens on 24 Hours, but you can switch to shorter or longer intervals to identify both sudden spikes and longer-term trends.

Tip:

• Use 1 Hour or 3 Hours to investigate recent spikes or incidents.
• Switch to 1 Week or 30 Days for capacity planning and to observe seasonal patterns (for example, daily backups or batch jobs that run weekly).

2.2.3 Graph Interactivity

• Hover Tooltips

  • Hovering over any point on the lines reveals the exact timestamp and metric value (e.g., CPU: 82% at 2025-05-30 14:00:00).

• Legend Toggles

  • Click a metric name (CPU, Memory, or Disk) in the legend to toggle that line on or off. This helps focus on a single resource if needed.

• Zoom & Pan

  • In some cases, you can click-and-drag to zoom into a narrower time window within the selected timeframe. Use the pan control or reset button to return to the full view.

---

3. Best Practices

• Monitor Baseline Usage

  • Use longer timeframes (1 Week or 30 Days) to establish baseline resource usage patterns. This helps you know what “normal” looks like and quickly spot anomalies.

• Investigate Spikes Immediately

  • When a server card shows a transient spike in CPU or memory, click into Server Details and set the timeframe to 1 Hour to see the exact duration and potential root cause (e.g., a cron job, deployment, or traffic surge).

• Evaluate Disk Growth Trends

  • If disk usage steadily climbs over days or weeks, drill into 2 Weeks or 30 Days to determine whether log files, backups, or dataset growth are responsible. Plan cleanup or capacity expansion accordingly.

• Identify Memory Leaks

  • A slow, continuous rise in memory usage across multiple timeframes can indicate a memory leak in your application or an unbounded cache. Investigate further by correlating memory trends with request patterns or job runs.

• Compare CPU vs. Memory

  • If CPU utilization is high but memory remains low (or vice versa), this indicates different bottleneck types (compute-bound vs. memory-bound). Use the legend toggles to isolate each resource line.

---

By leveraging the Servers index cards and the detailed Server Details view with interactive performance graphs, Laritor helps you proactively monitor infrastructure health, troubleshoot resource bottlenecks, and plan for future capacity needs.