Skip to main content
Metoro Exporter runs in each monitored Kubernetes cluster. It collects workload and cluster telemetry and sends it to the Metoro Hub. Monitored clusters use the metoro-exporter-onprem Helm chart. The Metoro Hub generates onboarding commands that point monitored clusters at the correct hub URLs and exporter chart version.

​
Exporter Architecture

​
Components

The exporter chart can run five primary components. Metoro Exporter is the cluster-local gateway. It watches Kubernetes resources, receives telemetry from local collectors and node agents, applies exporter-side processing, and sends data to the hub. Node Agent runs as a privileged DaemonSet on monitored nodes and collects node and workload telemetry with host access. OpenTelemetry Collector scrapes Prometheus-compatible targets and forwards metrics through the exporter. Target Allocator watches ServiceMonitor and PodMonitor resources and assigns scrape targets to collector replicas. Redis supports coordination between exporter and node-agent instances.

​
Data Flow

The exporter sends control-plane traffic to the hub apiserver and telemetry traffic to the hub ingester. In a standard deployment, monitored clusters need outbound network access to the hub deploymentUrl. For the hub-side components that receive this traffic, see Metoro Hub.