Pandastack Documentation
  • Welcome
  • Getting Started
    • Quickstart
      • Getting Started
    • Projects
      • Static Website
        • Configure your static website
          • Pre-defined ENV for static websites
      • Conatinered Website
        • How to configure nodejs project
        • How to Configure Python projects
        • How to Configure GO project
        • Docker runtime Projects
        • Private Connection with database.
        • Override default ENV
    • Databases
      • MySQL
      • PostgreSQL
      • Redis
      • MongoDB
      • TimeScaleDB
    • Monitoring
      • Uptime Check
      • SSL monitoring
      • Monitors pricing
    • Analytics
    • SSO
      • Google
      • Azure
    • Managed Apps
      • Wordpres
      • Directus
      • Strapi
      • Consul
      • Jenkins
    • PandaEdge
      • Deploy a nodejs function
      • Deploy a python function
      • Panda Edge pricing
Powered by GitBook
On this page
  • Monitoring Dashboard
  • Creating a Monitor
  • Monitor Details
  • Overview Metrics
  • Time-based Analysis
  • Charts and Visualizations
  • Alert Configuration
  • Available Metrics
  • Alert Conditions
  • Notification Methods
  • Managing Alerts
  • Managing Monitors
  • Best Practices
  1. Getting Started
  2. Monitoring

Uptime Check

The Monitoring Dashboard provides comprehensive uptime monitoring for your projects, allowing you to track availability, response times, and system metrics in real-time.

Monitoring Dashboard

The dashboard provides an overview of all your monitors with:

  • Uptime Statistics: View overall uptime percentage, number of down monitors, and paused monitors

  • Time Range Selection: Filter data for different time periods (1h, 6h, 24h, 7d, 30d)

  • Monitor Status: Each monitor shows:

    • Current status (UP/DOWN/PAUSED)

    • Last check time

    • Status message

    • Quick access to detailed view

Creating a Monitor

  1. Click "+ Add New Monitor" from the dashboard

  2. Configure General Settings:

    • Monitor Name: Enter a name (6 random characters will be appended automatically)

    • Project: Select the project to monitor (one monitor per project)

    • Heartbeat Interval: Check frequency in seconds (minimum 60s)

    • Retries: Maximum retries before marking as down

    • Request Timeout: Maximum time to wait for response

  3. Advanced Settings:

    • Max Redirects: Maximum number of redirects to follow (0 to disable)

    • Accepted Status Codes: Select which HTTP status codes indicate success

    • Certificate Options:

      • Enable certificate expiry notifications

      • Option to ignore TLS/SSL errors

  4. HTTP Options:

    • HTTP Method: GET, POST, or PUT

    • Request Body: For POST/PUT requests

    • Request Headers: Custom headers in JSON format

Monitor Details

Each monitor provides detailed insights:

Overview Metrics

  • Current response time

  • 24-hour average response time

  • 24-hour uptime percentage

  • 30-day uptime percentage

  • SSL certificate expiration (if applicable)

Time-based Analysis

  • Select time windows from 1 hour to 1 month

  • View historical uptime status

  • Response time trends

  • Container metrics (CPU/Memory) for associated projects

Charts and Visualizations

  • Response time graph

  • Uptime timeline

  • Resource utilization metrics

Alert Configuration

The monitoring system provides flexible alert configuration to help you stay informed about your service's health. You can create multiple alerts for each monitor with different conditions and notification methods.

Available Metrics

  • Response Time

  • Error Rate

  • CPU Usage

  • Memory Usage

  • Status Code

Alert Conditions

Each alert can be configured with:

  • Condition Type: Above, Below, or Equals

  • Threshold Value: The value that triggers the alert

  • Duration: Time (in minutes) the condition must persist before triggering

  • Severity Levels:

    • Info: For informational alerts

    • Warning: For potential issues

    • Critical: For serious problems

Notification Methods

Alerts can be delivered through multiple channels:

  • Email notifications

  • Slack integration

  • Webhook notifications (for custom integrations)

Note: Notification methods must be enabled in your notification settings before they can be used in alerts.

Managing Alerts

From the monitor details page, you can:

  • Create new alerts

  • Edit existing alert configurations

  • Delete unnecessary alerts

  • View alert status (Active/Triggered/Inactive)

Managing Monitors

From the monitor details page, you can:

  • Pause/Resume monitoring

  • Edit configuration

  • Delete the monitor

  • View active alerts

  • Configure notification settings

Best Practices

  1. Interval Selection:

    • Use shorter intervals (1-5 minutes) for critical services

    • Use longer intervals (15+ minutes) for non-critical monitoring

  2. Status Codes:

    • Include appropriate status code ranges based on your application

    • Consider 3xx codes if your application uses redirects

  3. Timeout Configuration:

    • Set timeouts based on expected response times

    • Account for network latency in timeout values

  4. Alert Configuration:

    • Set up meaningful thresholds based on service SLAs

    • Configure appropriate notification channels

    • Use different alert priorities for different conditions

PreviousMonitoringNextSSL monitoring

Last updated 3 months ago