Clickhouse
Status: not part of Eternaltwin. ClickHouse is not a storage backend you can select,
and nothing in the codebase talks to it. There is no ClickHouse dependency in
Cargo.toml or Cargo.lock, no ClickHouse client crate, and no ClickHouse key in
the configuration. If you are looking for the database Eternaltwin actually uses,
read Database.
ClickHouse is a column-oriented SQL database management system (DBMS) for online analytical processing (OLAP). It appears in the Eternaltwin project only as part of the observability stack running next to the application on the server: the 2024-11-02 hosting review budgets 50 GiB of disk for ClickHouse holding logs, traces and metrics, and the server page lists it as a service sitting next to the application. This page keeps the operator notes for that deployment.
How Eternaltwin emits telemetry
The application only speaks OpenTelemetry, configured in the [opentelemetry]
section:
[opentelemetry] enabled = true grpc_proxy_port = 4317 [opentelemetry.exporter] [opentelemetry.exporter.stdout] type = "Jsonl" color = "Auto" target = "eternaltwin://stdout"
Anything that stores those logs, traces and metrics, ClickHouse included, sits behind an OTLP collector and is invisible to Eternaltwin.
Installation
Config
Default path:
/etc/clickhouse-server/
Data directory:
/var/lib/clickhouse/