Coolify Sentinel

Why it's ranked here

The design suits an always-running host agent: Rust, SQLite, bounded query admission, separate read and write database connections, configurable retention, and Docker packaging keep the operational model focused. Optional traffic aggregation adds useful depth without storing raw requests.

What's good

Health and version probes remain public, while metrics require bearer authentication with constant-time token comparison. Storage sampling and expensive volume walks use separate schedules. Traffic analytics retain aggregate rollups instead of raw requests, and the repository includes OpenAPI documentation plus reproducible benchmark tooling.

Tradeoffs

Production deployment targets Linux, and Docker metrics require access to the Docker socket. Accurate volume sizing needs relevant host paths mounted into the container, while large directory walks can be slow. Traffic analytics require both a compile-time feature and runtime opt-in. The Coolify proxy wiring and rendering interface live outside this repository.

How to use it well

Use it as a small host-side metrics agent for Coolify-managed Linux servers, especially when you want local history, Docker visibility, push delivery, and optional proxy-log analytics. Mount only the storage paths you need and tune collection intervals carefully. It does not provide the Coolify dashboard, proxy configuration, or full integration layer.

Observed

License

Apache-2.0

Primary language

Rust

Packaging and installation

Published Docker image, local Docker build, and Cargo build or run workflows

Interface

Bearer-authenticated REST API with public health and version endpoints

API specification

OpenAPI 3.0 specification is included

Platform support

Linux production environment with Docker required for container metrics

Storage

Bundled SQLite stores historical metrics with configurable retention

Architecture

Cargo workspace separates API, collector, push, store, configuration, Docker, and traffic components