When a ClickHouse® database node goes down, most admin tools stop working because they depend on the HTTP interface. CHOps Pro solves this with Remote Cluster Management.
The problem
A ClickHouse® node becomes unresponsive. Maybe it ran out of memory, a config change broke something, or an upgrade failed. Your monitoring dashboard shows the node is down, but you cannot query it, view its logs, or restart the service through the normal HTTP interface.
The traditional fix: SSH into the server, navigate to the logs directory, read through log files, edit configuration, and restart the service manually. This requires SSH access, knowledge of the server layout, and is slow under pressure.
How Remote Cluster Management works
CHOps Pro deploys a lightweight proprietary binary on each ClickHouse® node. This binary communicates with the CHOps application over encrypted channels and runs independently of the ClickHouse® process.
Through this binary, you can:
- View server logs directly from the filesystem, even when ClickHouse® is not running
- Update configuration files (users.xml, config.xml, custom configs) from the browser
- Start, stop, and restart ClickHouse® services with a single click
All of this happens from the CHOps web interface. No SSH required. No VPN. No command-line knowledge.
When this matters
Remote Cluster Management is most valuable during incidents. At 2 AM when a node crashes, your on-call engineer opens CHOps, reads the logs to understand what happened, fixes the config if needed, and restarts the service. Total time: minutes instead of the 30+ minutes it typically takes with SSH.
It is also valuable for teams with strict access control policies where not everyone has SSH access to production servers.
Getting started
Remote Cluster Management is available in CHOps Pro. Book a demo to see it in action.
