v0.7.0 Windows Preview

Experimental native Windows support for StatLite 0.7, aimed at developers who use Windows as their primary development environment, including those building Spring Boot, Quarkus, Micronaut, and other supported applications.

This preview provides the same application monitoring, configuration, SQLite history, and browser dashboard functionality as StatLite 0.7, with the Windows limitations described below. It runs as a foreground console application and can monitor local or remote applications.

Requirements

• Windows 10 or later, x64 (AMD64), with PowerShell and a modern browser. Native automated validation ran on Windows Server 2022; Windows 10 desktop validation is pending.
• A writable local folder for the executable, configuration, and SQLite database.
• For application monitoring, a running application with a supported metrics endpoint reachable from Windows.

Go, Java, a C compiler, WSL, and Docker are not required to run StatLite. Your monitored application may have its own prerequisites.

Download and start

Download the Windows AMD64 ZIP, extract it, and run from the extracted folder:

.\statlite.exe

Open http://127.0.0.1:9090. The bundled statlite.yml is an example configuration for self-monitoring. Keep the terminal open; press Ctrl+C to stop. The archive contains statlite.exe, the self-monitoring example statlite.yml, and the StatLite, Chart.js, and Orbitron license files.

Try StatLite first

Use the bundled self-monitoring example:

.\statlite.exe

Open http://127.0.0.1:9090. The example file includes a comment identifying it as a self-monitoring configuration.

Configure an application

For Spring Boot with Actuator endpoints exposed on port 8080, stop the default run, then run:

.\statlite.exe inspect 'http://localhost:8080' --create-config .\statlite.yaml
.\statlite.exe

For a remote application, replace the URL with its reachable base URL. For Quarkus or Micronaut, use one of these commands to create the configuration, then run .\statlite.exe:

.\statlite.exe inspect --type quarkus 'http://localhost:9000' --create-config .\statlite.yaml
.\statlite.exe inspect --type micronaut 'http://localhost:8080' --create-config .\statlite.yaml

Other supported applications require their StatLite metrics endpoint first; see the integration guides and configuration reference. Inspection does not accept credentials; configure authenticated targets manually using the reference.

Generate traffic and allow a few polling intervals for history. Restart with the same configuration to retain history. Relative SQLite paths resolve from the configuration directory. Use a writable local folder, preserve the database, and quote paths containing spaces. An absolute database path can use forward slashes:

storage:
  sqlite_path: 'C:/Users/your-name/StatLite/statlite.sqlite'

Keep the dashboard bound to 127.0.0.1: it has no built-in dashboard or API authentication.

Known limitations and validation

• Experimental Windows AMD64 console build only. No ARM64 binary, installer, package manager, Windows Service integration, or automatic startup.
• Local Windows host CPU, memory, and disk collection is unavailable. Missing values appear as no data or hidden panels and may produce diagnostic warnings. Application endpoint metrics remain available; remote application metrics describe the application environment, not this workstation.
• Windows 10 desktop, browser presentation, and interactive terminal Ctrl+C validation remain pending. CI verifies shutdown with Ctrl+Break through the same Go interrupt handler. Remote-network and authentication behavior are outside that smoke test.
• This is the exact executable retained by successful Windows CI, from commit cb1876fac1d5995f79923ba6de805b53ba0e02d9. It reports v0.7.1-dev in --version and health output because that is the tested branch version; it was not rebuilt or relabeled for this preview.
• CI passed native Go tests, storage integration, static analysis, dashboard tests, and startup, Spring collection, graceful shutdown, SQLite integrity, preserved history, and restart checks on Windows Server 2022. Other integrations have not been individually certified on Windows.

If startup fails, check terminal output, config paths, database permissions, and whether port 9090 is occupied. For collection failures, check endpoint reachability and metrics exposure.

Feedback

Join Windows Preview: Feedback and Feature Requests.

Tell us about installation or runtime problems and which Windows-specific features you would use. This preview will help assess demand for native Windows support.

This is an isolated pre-release. Stable releases and Linux/macOS distribution channels are unchanged.