Web & Application Servers
    Updated May 2026
    OpenLiteSpeed logo

    OpenLiteSpeed Monitoring

    Monitor OpenLiteSpeed request rate, LSCache (Public/Private) hit ratio, virtual host status, external app workers, and SSL connections in real time — agent-based via the native `.rtreport` stat file.

    Start Free TrialView Docs

    Why monitor OpenLiteSpeed?

    OpenLiteSpeed is the open-source LiteSpeed edition — the engine behind most CyberPanel WordPress hosting, plus Docker, Kubernetes, and Magento deployments. Cache regressions, per-vhost slowdowns, and external app failures degrade sites silently. Monitoring surfaces problems while there's still time to fix them.

    Auto-discovery via Xitogent — zero manual configuration
    Real-time request rates and end-to-end response time metrics
    LSCache Public and Private hit-ratio tracking, separated for accurate cache tuning
    Static vs dynamic hit ratio for per-vhost cache-efficiency analysis
    Per-virtual-host request status and external-application worker monitoring
    Connection-state tracking (HTTP, HTTPS, keep-alive)
    HTTP and HTTPS throughput split (BPS_IN, BPS_OUT, SSL_BPS_IN, SSL_BPS_OUT)
    Customizable alert thresholds for every metric
    1-minute metric collection intervals out of the box
    Historical data retention for capacity planning and post-incident review
    What is OpenLiteSpeed monitoring?

    OpenLiteSpeed monitoring, explained

    OpenLiteSpeed monitoring catches cache regressions, worker saturation, and per-virtual-host slowdowns before they hit your users — critical for CyberPanel WordPress hosts and any multi-site OLS deployment. Xitoring auto-discovers your OLS instance, polls the same .rtreport stat file the WebAdmin Console reads, and surfaces per-vhost cache and connection metrics in one dashboard — with alerts routed to Slack, PagerDuty, Telegram, or wherever your team already responds.

    Metrics

    What we monitor

    Requests / sec

    Live HTTP request rate served by OLS, broken down by virtual host. The first signal for traffic surges and attacks.

    Pub Cache Hits / sec

    LSCache public-cache hits per second — the headline ranking metric for WordPress + LSCWP setups. Sustained values close to total request rate mean LSCache is working.

    Private Cache Hits / sec

    LSCache private-cache hits — logged-in user pages and personalized content. Tracked separately so a logged-in cache regression doesn't hide behind public-cache numbers.

    Static Hits / sec

    Static-asset hits per second. The static-vs-dynamic ratio drives `cacheLookup` tuning in your VirtualHost configuration.

    Request Processing

    Current requests in-flight per virtual host. Sustained non-zero values mean handler workers can't drain the queue.

    Response Time

    End-to-end latency to serve a request. Track p50, p95, and p99 to catch tail-latency regressions invisible to averages.

    HTTP / HTTPS Connections

    Active HTTP and HTTPS connections, separated. SSL Connections approaching `SSLConfig` worker limits triggers TLS handshake failures before regular requests degrade.

    BPS_IN / BPS_OUT

    Bytes-per-second throughput on plain HTTP. Anomalies often surface here before they show up in request counts.

    SSL_BPS_IN / SSL_BPS_OUT

    Bytes-per-second throughput on HTTPS. Separate from plain HTTP for cleaner diagnosis of TLS-specific issues.

    External Application Status

    Status and worker count for LSPHP / LSAPI external applications. Catches PHP slowdowns inside OLS before they cascade to user-visible 5xx errors.

    Virtual Host Status

    Per-vhost request-processing status. Lets you isolate which site or domain is degraded when overall numbers look fine — critical for shared hosting.

    Triggers & Alerts

    Configurable alert triggers

    Set up custom triggers in your dashboard to get notified the moment OpenLiteSpeed metrics cross your defined thresholds.

    OpenLiteSpeed monitoring trigger configuration dashboard

    Request Rate

    warning

    Fires when request rate exceeds threshold.

    Cache Hit Ratio

    warning

    Triggers when cache ratio drops.

    Response Time

    critical

    Alerts on high response latency.

    Connections

    critical

    Fires when connections approach limits.

    01

    Importance of OpenLiteSpeed Monitoring

    OpenLiteSpeed powers cost-effective, high-performance web hosting. Without monitoring, cache inefficiencies and connection issues go undetected.

    • Track cache performance to maximize speed
    • Monitor connections to prevent bottlenecks
    • Detect response time degradation early
    • Ensure optimal resource utilization
    OpenLiteSpeed monitoring dashboard
    OpenLiteSpeed cache analytics
    02

    Why Choose Xitoring

    Zero-config setup with instant metric collection and flexible alerting.

    • One-command install
    • 15+ global monitoring nodes
    • Unified dashboard
    • Multi-channel alerting
    • Historical data retention
    Xitoring overview
    Alert configuration
    Use cases

    Common OpenLiteSpeed monitoring scenarios

    Where OpenLiteSpeed typically runs today — and what could go wrong if no one's watching.

    Fast WordPress sites

    WordPress sites built on OpenLiteSpeed use its built-in caching to feel almost instant. When that cache stops working as expected, page speed drops and visitors quietly bounce. We catch the dip the moment it begins so search rankings and conversions aren't quietly hurt.

    OpenLiteSpeed running inside containers

    When the web server runs inside containers, the platform constantly moves it around — and one server can end up doing far more work than the others. We surface the imbalance so the team can rebalance before some visitors get a slower experience than others.

    Busy online stores

    Online stores hit the web server hardest at checkout — the exact moment a slow page costs real revenue. We watch the signals that show whether the store can handle a traffic spike so the team can prepare for promotions and sales with confidence.

    Before you start

    Prerequisites for OpenLiteSpeed

    Make sure you've got these in place — most installs are a 60-second job once they are.

    • OpenLiteSpeed 1.x (current 2026 line) installed and running
    • OpenLiteSpeed stats path accessible (default /tmp/lshttpd/, or /dev/shm/ols/status/ for RAM-disk setups)
    • Root access on the host to install Xitogent
    Setup Guide

    Get started in minutes

    1

    Install Xitogent on your server

    Install the lightweight Xitogent monitoring agent on the host running OpenLiteSpeed.

    curl -s https://xitoring.com/install.sh | sudo bash -s -- --key=YOUR_API_KEY
    2

    Confirm the stats path

    OpenLiteSpeed writes runtime stats to `/tmp/lshttpd/` by default. Confirm that path exists and contains active stat files — Xitogent will prompt for it during integrate (defaults match).

    sudo xitogent integrate
    3

    Enable the OpenLiteSpeed integration

    Use the Xitoring dashboard or CLI to enable the OpenLiteSpeed integration. Xitogent auto-detects your OpenLiteSpeed instance and configured virtual hosts.

    4

    Configure alert thresholds (optional)

    Set custom thresholds for Request Rate, Cache Hit Ratio, or Response Time to catch traffic anomalies and cache regressions early.

    5

    Verify it's working

    Run this command on the server to confirm Xitogent picked up the integration. Fresh metrics will start streaming to your dashboard within ~30 seconds.

    sudo xitogent status
    Compare

    Considering alternatives?

    See how Xitoring stacks up against the alternatives for OpenLiteSpeed monitoring — flat pricing, deeper integrations, and one agent that covers your whole stack.

    See all comparisons

    Frequently asked questions

    What is OpenLiteSpeed monitoring?
    OpenLiteSpeed monitoring is the continuous collection of OLS performance data — request rate, LSCache Public/Private hit ratio, static vs dynamic hits, virtual host request status, external application worker counts (LSPHP/LSAPI), and HTTP/HTTPS throughput — combined with alerting when those metrics breach thresholds. The data comes from the same `.rtreport` stat file the OLS WebAdmin Console reads.
    OpenLiteSpeed vs LiteSpeed Enterprise — what's the difference for monitoring?
    OLS and Enterprise share the same event-driven core and LSCache engine, so the core metric vocabulary is identical: request rate, cache hits (Pub/Private/Static), connections, throughput, virtual-host status. Enterprise adds anti-DDoS Blocked IPs, advanced ModSecurity engine, and ESI (Edge Side Includes) for LiteMage on Magento — those metrics don't exist in OLS. Use the dedicated LiteSpeed integration for Enterprise; this OpenLiteSpeed integration for the open-source build.
    How do I enable Real-Time Stats in OpenLiteSpeed?
    Real-Time Stats is enabled by default — OLS writes to `.rtreport` in `/tmp/lshttpd/` automatically. To verify, check `ls -la /tmp/lshttpd/.rtreport`. If the file is missing, restart OLS (`/usr/local/lsws/bin/lswsctrl restart`) and confirm `Server Health Status` is enabled in the WebAdmin Console at `https://server:7080`. For RAM-disk performance, point the path to `/dev/shm/ols/status/`.
    How do I monitor LSCache hit ratios on OpenLiteSpeed?
    Xitoring reads `Pub Cache Hits/sec` and `Private Cache Hits/sec` directly from the `.rtreport` stat file (the same source the WebAdmin Console uses). Verify individual responses are cached by checking the `x-litespeed-cache: hit` response header. Set an alert when the public-cache hit ratio drops below your baseline (typically 80%+ for a well-tuned WordPress + LSCWP site).
    How do I monitor OpenLiteSpeed on CyberPanel?
    CyberPanel installs OLS to `/usr/local/lsws/` with stats at the standard `/tmp/lshttpd/` path. Install Xitogent (`curl -s https://xitoring.com/install.sh | sudo bash -s -- --key=YOUR_API_KEY`), enable the OpenLiteSpeed integration with `sudo xitogent integrate`, and metrics start streaming. CyberPanel's per-website resource isolation maps cleanly to OLS virtual hosts, so per-site metrics work out of the box.
    Can I monitor OpenLiteSpeed in Docker or Kubernetes?
    Yes. The official `litespeedtech/openlitespeed` Docker image writes `.rtreport` to `/tmp/lshttpd/` inside the container — mount that path as a writable volume and Xitogent (running as a sidecar or on the host) reads from it. For Kubernetes, deploy Xitogent as a DaemonSet with the volume mounted from each OLS pod.
    Will Xitogent affect OpenLiteSpeed performance?
    No measurable impact. Xitogent reads the existing `.rtreport` file OLS already writes for its own WebAdmin Console — there is no extra request handling, no instrumentation injected into the request path, no API calls. The polling interval (60 seconds by default) generates negligible disk I/O.
    Can I integrate OpenLiteSpeed with Prometheus or Grafana?
    Yes — the official `litespeedtech/` provides Prometheus-format metrics from the same `.rtreport` data. Xitogent reads the file directly (no exporter required) but the integration is compatible with environments that already run the LiteSpeed Prometheus Exporter for Grafana dashboards.
    What OpenLiteSpeed versions are supported?
    OpenLiteSpeed 1.x — including the current 1.7+/1.8 series in 2026 — is fully supported. The `.rtreport` stat-file format is stable across the 1.x line, so the integration is forward-compatible. For HTTP/3 (QUIC) connection metrics, OLS 1.7+ is required.

    Start monitoring OpenLiteSpeed today

    Set up in under 60 seconds. No credit card required. Full metrics from day one.

    Start Free Trial

    Keep exploring

    Related Integrations