Skip to main content
This deployment brings Metoro directly into your infrastructure. While we strive to make installation and maintenance as boring as possible, it often helps to know how Metoro is architected so you can understand what you’re running and how to operate it.

​
Architecture Overview

Metoro consists of two main parts:
  1. Metoro Hub The central control plane that processes, stores, and serves observability data. In the cloud installation, this is managed by Metoro, but here you deploy and manage it yourself.
  2. Metoro Agents Lightweight agents deployed on each Kubernetes cluster that collect and forward data to the hub. These run the same way as the cloud installation.
We recommend that Metoro is deployed in a hub and spoke architecture. One organization wide instance of the Metoro Hub into which all telemetry feeds. This has a number of benefits:
  1. Comparison of data and services across clusters is possible
  2. Operationally less overhead, one installation of stateful components is easier to handle than N.
  3. Resource efficient, each Metoro installation comes with fixed overhead, centralizing it leads to less waste and more efficient resource usage.

Metoro Hub

The self-hosted control plane, data stores, UI/API, ingestion, and workflow components.

Metoro Exporter

The lightweight per-cluster components that collect telemetry and send it to the hub.