Use case · Analytics
ClickHouse with controlled configuration and readiness
Sysaro manages only its own ClickHouse config fragment, leaves vendor/manual configuration intact and verifies the service after apply.
Verified against public version: 0.20.02026-09-15Factual boundary · roadmap is not presented as shipped
For ClickHouse, Sysaro stores typed desired state, previews the managed file, atomically applies a Sysaro-owned config.d fragment, restarts the service, probes readiness and restores the previous file on failure.
Managed parameters
| Area | Current boundary |
|---|---|
| Network | Listen address, HTTP port, native TCP port |
| Capacity | max_connections, max_concurrent_queries |
| Ownership | Only /etc/clickhouse-server/config.d/90-sysaro.xml |
| Verification | Restart + loopback /ping readiness using the managed HTTP port |
Why a fragment instead of the whole config.xml
Sysaro should not become the owner of every ClickHouse setting merely to provide a GUI. A drop-in fragment keeps vendor, manual and managed settings separable.
Preview shows the exact path, content and SHA-256 before apply.