Skip to main content
Metoro Exporter is the central service inside a monitored cluster. It receives telemetry from local collection components, watches Kubernetes resource state, applies exporter-side processing, and sends data to the Metoro Hub.

​
Talks To

​
How It Fits

Metoro Exporter is the bridge between the monitored cluster and the hub. Node agents send workload telemetry to it, OpenTelemetry collectors send scraped metrics to it, and the exporter itself watches Kubernetes resources so the hub can understand cluster state. The service uses the hub apiserver for control-plane configuration such as exporter-side filtering and redaction settings. Telemetry and Kubernetes resource updates are forwarded to the hub ingester using the onboarding token and hub URLs generated by the Metoro Hub. Redis is used for coordination data shared with node agents and exporter replicas. The exporter does not store durable telemetry locally; the hub ingester and ClickHouse are the durable telemetry path.

​
Operational Notes

Metoro Exporter runs as a Deployment and can be scaled horizontally as cluster telemetry volume grows. The chart includes a horizontal pod autoscaler for this service, and the default deployment keeps more than one replica available. Exporter availability affects the local forwarding path. If exporter pods are unhealthy, node agents and collectors may still be running, but telemetry cannot reliably leave the monitored cluster.