Overview

Metoro Hub is the self-hosted control plane for an installation. It receives telemetry from monitored clusters, stores that data, serves the UI and API, and runs background workflows. The hub is installed with the metoro-onprem Helm chart.

​

Hub Architecture

​

Components

The hub contains five primary components:

• Apiserver is the UI and API entry point. It handles user and automation traffic, reads metadata from PostgreSQL, queries telemetry from ClickHouse, and starts workflow-backed behavior through Temporal.
• Ingester is the telemetry write path. It receives data from monitored clusters, normalizes and batches it, and writes it to ClickHouse.
• ClickHouse stores high-volume telemetry such as metrics, traces, logs, profiling data, and Kubernetes state.
• PostgreSQL stores control-plane metadata and Temporal persistence.
• Temporal runs durable background workflows such as alert evaluation, scheduled jobs, notifications, and AI SRE workflows.

When the stateful services are bundled, the chart uses the Altinity ClickHouse Operator for ClickHouse and the CloudNativePG operator for PostgreSQL. Apiserver, Ingester, and Temporal are stateless service layers that can be scaled horizontally as load requires. Durable metadata, workflow state, and telemetry are held by PostgreSQL and ClickHouse.

​

Data Flow

Users connect to the hub through the apiserver and UI. Monitored clusters send exporter API traffic to the apiserver and telemetry ingestion traffic to the ingester. The apiserver uses PostgreSQL for metadata. The ingester writes telemetry to ClickHouse. Temporal coordinates longer-running workflows. For the full deployment diagram, see Architecture Overview.