ClusterWare User Guide
  • 👋Welcome to ClusterWare!
  • Learning Path
    • 🔭Overview
    • 1️⃣Create a distributed NodeJS application in 10 minutes
      • Step 1: Create a new cluster
      • Step 2: Onboard servers to ClusterWare
      • Step 3: Install server software
      • Step 4: Create application instances
      • Step 5: Import application source code
      • Step 6: Start the application
      • Step 7: Create and start application load balancer
    • 2️⃣Uniformly secure access to your infrastructure
      • Step 1: Create Security Policy
      • Step 2: Install Firewall
      • Step 3: Apply Security Policies
    • 3️⃣Secure the data in-transit with SSL
      • Step 1: Gateway Security
      • Step 2: Endpoints Security
    • 4️⃣Eliminate a single point of failure in 10 minutes
      • Step 1: Onboard a new server
      • Step 2: Install Niginx
      • Step 3: Configure DNS
      • Step 4: Create and start the failover load balancer
      • Step 5: Run a load balancer outage experiment
  • Fundamentals
    • 🧩Sync, Insights, Tasks
    • 🤖Supported Technologies
    • 🛡️Server Authentication Methods
    • 💡Connectivity Troubleshooting
  • Services
    • Clusters
      • Cluster Selection & Creation
      • Editing Cluster
      • Notification Subscriptions
      • Auto-deployment (CI/CD)
    • Dashboard
      • Load Balancers & Applications
    • Servers
      • Create/Edit Server
      • Status
      • Software
      • Security
        • Enabling Non-Root Firewall Status Checking
        • Changing Firewall Status
        • Applying Security Policies
      • Metrics
      • Alerts
    • Applications
      • Create/Edit Application
      • Status
      • Git
      • Output Log / Error Log
      • Metrics
      • Alerts
    • Load Balancing
      • Create/Edit Load Balancer
      • Status
      • Gateway Security
      • Endpoint Security
    • Security Policies
      • Create/Edit Security Policy
Powered by GitBook
On this page
  • Overview
  • Chart Controls
  • Date Range
  • Metric Types
  • Show/Hide Plots
  • Metric Charts
  • CPU Load
  • Memory Usage
  • Disk Usage
  • Firewall Status
  • Automatic Metric Period Selection
  1. Services
  2. Servers

Metrics

PreviousApplying Security PoliciesNextAlerts

Last updated 11 months ago

Overview

Chart Controls

Date Range

  • From: Start date of the metrics data.

  • To: End date of the metrics data.

Maximum time range for metrics query is 30 days.

Metric Types

  • CPU Load

  • Memory Usage

  • Disk Usage

  • Firewall Status

Show/Hide Plots

Users can toggle the visibility of individual plots by clicking on the corresponding items in the plot legend. Plots that are excluded from the chart are indicated with a strikethrough in the legend.

Metric Charts

CPU Load

Avg

Average of 5 min load

%

Min

Lower bound of 5 min load

%

Max

Upper bound of 5 min load

%

Notification

CPU load threshold

%

Memory Usage

Avg

Average memory usage

MB

Min

Minimum memory usage

MB

Max

Maximum memory usage

MB

Total

Total memory available

MB

Notification

Memory usage threshold

MB

Disk Usage

Used

Average of 5 min load

MB

Total

Lower bound of 5 min load

MB

Notification

Disk usage threshold

MB

Firewall Status

Firewall Enabled

If the Firewall is enabled or not

1=Yes, 0=No

Policies Not Applied

Number of policies that are not applied

Count

Extra Rules Applied

Number of extra firewall rules applied

Count

Automatic Metric Period Selection

ClusterWare's automatic period selection feature is designed to optimize the granularity of metrics displayed based on the selected date range and available data points. This ensures that users get the most detailed and relevant insights without overwhelming them with too much information.

ClusterWare samples metrics with 1, 5 and 15 min intervals depending on your account type.

Time range from (inclusive)
Time Range to (exclusive)
Period

0

1

1 min

1

2

5 min

2

4

1 h

4

8

6 h

8

31

1 d

CPU load is relative to the number of CPU cores. For instance the maximum load of a 12 core CPU is 1200%. 200% load could mean that 2 CPU cores are working under maximum load or 10 CPU cores are working at 20% load. .

Read more about Linux CPU load