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
  • Cluster Diagram
  • Tiers
  • Unassociated Applications
  • Status Indicators
  • Traffic Flow Status
  • Application Instance Status
  1. Services
  2. Dashboard

Load Balancers & Applications

PreviousDashboardNextServers

Last updated 10 months ago

Overview

This section provides a holistic view of all load balancers and applications in the cluster. Here you can inspect how the components of the cluster are associated with each other and how the traffic is expected to flow.

If you have multiple load balancers in your cluster, they will be displayed one by one on this dashboard along with all applications associated with them.

Cluster Diagram

Tiers

  • Users (tier 0): Shown as cloud icon. Indicates traffic coming from the Internet.

  • Load Balancer (tier 1): This is the topmost element. It shows the name and the URL endpoint of the load balancer which handles the distribution of incoming traffic to the applications.

  • Applications & Servers (tier 2): An application is a "container" encapsulating one or more instances running on a single server. Each application is tagged with the server it is deployed on.

  • Application Instances (tier 3): These boxes represent individual instances of each application. Each instance is an application process running on the specified server and port.

By running multiple single-threaded processes (application instances) on a server you can maximize server utilization and achieve higher availability.

Unassociated Applications

If the cluster contains applications not associated with any load balancer, ClusterWare shows information about them in the bottom of this section.

Status Indicators

Traffic Flow Status

  • Animated arrow - traffic flowing normally: It means that all applications are running and are included in the load balancer config.

  • Static arrow - no traffic flowing: It may indicate for example that some applications are not included in the load balancer config.

  • Warning icon - disruption in traffic flow: For example when not all application instances are running.

Application Instance Status

  • Animated green cog: represents a running application instance.

  • Static yellow cog: represents a stopped application instance or an application instance pending start.