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
  • Logs of Application Instances
  • Sync Actions
  • Differences between Output and Error Log
  1. Services
  2. Applications

Output Log / Error Log

PreviousGitNextMetrics

Last updated 11 months ago

Overview

ClusterWare offers a streamlined approach to accessing and navigating through log files for individual application instances. In services with multiple application instances, the ClusterWare Console simplifies the process of locating and examining the logs of problematic instances.

Logs of Application Instances

Users can easily switch between instances using the accordion menus and view their logs without leaving the current screen.

By design ClusterWare displays insights captured at the time of sync with the server. Therefore to display new logs generated after the last sync the user needs to use Sync Logs action.

Sync Actions

  • Logs: Syncs all output and error logs generated on the server for all instances.

Differences between Output and Error Log

Output Log

The output log captures all the standard output (stdout) generated by the application. This includes all the information that the application writes to the console using methods like console.log, console.info, and similar. Output Log has white text color.

Error Log

The error log captures all the standard error output (stderr) generated by the application. This includes error messages, warnings, stack traces, and any other critical issues that the application encounters and writes using methods like console.error, console.warn, or when an exception is thrown. Error Log has orange text color.