-
Hello, I'd like to use this tool to manage backup and restore of several different clickhouse shards my team currently runs on a kubernetes cluster. To streamline and simplify things, we've decided to use the API, but we'd like to get the same verbose output we get when running the cli on a shard pod directly. When run on a specific shard, the cli outputs a bunch of great log info detailing the steps of the backup process along with timestamps for each action. Is there a way to capture this information when working through the API? At most, the /backup/status endpoint will return a fairly simple json object containing the backup name, when it started, and when it ended, but we don't get insight into the steps taken during the backup. Is there a flag we can trip to get this verbose output? If not, this would be a great quality of life feature to add, as collecting verbose debug data will help us ensure we haven't taken an incomplete backup and help identify what happened when something goes wrong. Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
use in your pod template spec:
containers:
- name: clickhouse-backup
image: altinity/clickhouse-backup:latest
environment:
- LOG_LEVEL=debug or configure via ConfigMap /etc/clickhouse-backup/config.yml
|
Beta Was this translation helpful? Give feedback.
use in your pod template
or configure via ConfigMap /etc/clickhouse-backup/config.yml
api server
show their log to stdout of container