Connect your application
Choose an integration and get a minimal configuration you can run right away.
Connect Spring Boot, Quarkus, Micronaut, Caddy, Javalin, FastAPI, Express, Django, Gin, or Go net/http to lightweight self-hosted monitoring without deploying a full Prometheus and Grafana stack.
See the dashboard before setting up: Explore the demo (uses simulated data).
Choose an integration
Not sure? Choose Inspect.
Application details
Caddy setup required
Monitor HTTP traffic through Caddy
Requires StatLite 0.7.0+. No application instrumentation is required. Tested with Caddy 2.11.4, an explicit named HTTPS site, and one direct reverse_proxy. Add this inside Caddy’s existing global options block:
metrics {
per_host
}Send a request to your site, then find caddy_http_request_duration_seconds_count in the metrics scrape and copy its exact host label. Configure one StatLite target per host. Keep the metrics endpoint private; the default admin listener should remain on loopback. For Docker, use a dedicated read-only metrics listener on a private network as described in the guide.
Charts show requests, HTTP errors, and average response time measured at Caddy. Application health, CPU, memory, and restart detection are unavailable. UP means metrics collection works, even when the upstream returns 502.
Wait for two usable polls after generating traffic. The first establishes a baseline. Caddy is not supported by statlite inspect or the CLI configuration writers; save the YAML generated here manually.
Application setup required
Enable Spring Boot Actuator
Add Spring Boot Actuator and expose its health and metrics endpoints. StatLite works with standard Actuator metrics; Prometheus metrics are optional. Generated YAML uses /actuator as the management base URL.
Application setup required
Enable Quarkus metrics
Add quarkus-micrometer-registry-prometheus to expose /q/metrics. Add quarkus-smallrye-health if you also want application health reporting.
Application setup required
Enable Micronaut metrics
Requires StatLite 0.6.0+. Enable Micronaut management and Micrometer to expose /prometheus. Generated YAML uses this metrics endpoint.
Application setup required
Add StatLite Metrics to your app
Generated YAML configures StatLite. You must also add the helper, middleware, or view and expose /statlite/metrics in your application. The Express article walks through that pattern.
FastAPI
Express
Django
net/http
Gin
Javalin
These lightweight integrations keep cumulative state in the application process. Use one stable endpoint and StatLite target per process unless your application provides its own aggregation.
Live preview
statlite.yaml
Using a custom endpoint or management path? Edit the generated YAML before starting StatLite.
Let StatLite help
Not sure which integration to use?
Let StatLite inspect your application locally. The browser will not connect to your app.
statlite inspect http://localhost:8080
StatLite will try to detect a supported integration. If successful, it will show the available capabilities and print a suggested statlite.yaml.
For Micronaut, select the type explicitly: statlite inspect --type micronaut 'http://localhost:8080'.
For Caddy, choose Caddy above and save the generated YAML manually. Inspect does not support Caddy.
Read the Inspect documentation