A lightweight, self-hosted metrics dashboard with a small memory and operational footprint, designed for applications running on VPSs and small servers. A single Go binary monitors Spring Boot applications through Actuator and other applications that expose a small, fixed JSON metrics endpoint, without requiring Prometheus or Grafana. It stores focused health, traffic, latency, CPU, memory, and optional host metrics in SQLite.

Website: pvrlabs.xyz/statlite

StatLite is built for resource-constrained servers. Low memory, CPU, disk, and operational overhead are treated as product constraints.

Learn how to set up lightweight Spring Boot monitoring without Prometheus and Grafana.

docker run --rm \
  -p 127.0.0.1:9090:9090 \
  ghcr.io/pvrlabs/statlite:latest

Open http://127.0.0.1:9090. StatLite monitors itself by default, so the dashboard starts with live data.

See the Docker guide for persistent storage, container networking, local builds, and access guidance.

StatLite is intentionally focused and is not a replacement for Prometheus and Grafana.

Install the latest release on macOS or Linux:

curl -fsSL https://raw.githubusercontent.com/PVRLabs/statlite/main/install.sh | sh

Or install with Homebrew:

brew install pvrlabs/tap/statlite

See Installation for supported platforms, custom install locations, source builds, and server-wide Linux setup.

Start with an application's base URL. StatLite can identify a supported integration and print a minimal, runnable statlite.yaml:

statlite inspect 'http://localhost:8080'

The command checks the conventional Spring Boot Actuator and StatLite Metrics v1 paths, then prints the detected endpoint, available capabilities, a minimal configuration, and the next command. It is bounded and read-only: it does not require or create statlite.yaml, open SQLite, or start monitoring.

For a new Spring application, the successful output includes a complete minimal configuration:

server:
  listen: "127.0.0.1:9090"

storage:
  sqlite_path: "./statlite.sqlite"

polling:
  interval: "30s"

targets:
  - name: "app"
    type: "spring"
    actuator_base_url: "http://localhost:8080/actuator"

For a new setup, save the configuration as statlite.yaml. If you already have a configuration, copy only the target entry into its targets list. Then run:

statlite

See Configuration for discovery limits, authentication limitations, all settings, and manual target configuration. See examples/ for Spring Boot, Python/FastAPI, self-monitoring, and multi-target configurations.

• Spring Boot Actuator: Collects health, request, JVM, process, and optional host metrics from Actuator endpoints.
• StatLite Metrics v1: A small, fixed JSON endpoint that applications in any language or framework can implement.
• StatLite self-monitoring: StatLite can report its own health, traffic, process, and host metrics.

Depending on the integration, StatLite can also collect CPU, memory, and disk metrics for the environment running the application.

• Installation
• Docker
• Configuration
• Monitoring on resource-constrained servers
• StatLite Metrics v1
• systemd deployment
• Product and architecture
• Storage and schema direction
• Spring Boot guide
• Examples

MIT