> ## Documentation Index
> Fetch the complete documentation index at: https://metoro.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Metoro Exporter components

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

```mermaid theme={null}
graph TB
    subgraph "Monitored Cluster"
        K8S[Kubernetes API]
        W[Workloads and nodes]
        NA[Node Agent]
        E[Metoro Exporter]
        OC[OpenTelemetry Collector]
        TA[Target Allocator]
        R[(Redis)]

        W --> NA
        K8S --> E
        K8S --> TA
        TA --> OC
        OC --> E
        NA --> E
        E <--> R
        NA <--> R
    end

    E -->|Control-plane API| API[Hub Apiserver]
    E -->|Telemetry| I[Hub Ingester]
```

## Components

The exporter chart can run five primary components. [**Metoro Exporter**](/docs/on-premises/10.x/architecture/metoro-exporter/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**](/docs/on-premises/10.x/architecture/metoro-exporter/components/node-agent) runs as a privileged DaemonSet on monitored nodes and collects node and workload telemetry with host access. [**OpenTelemetry Collector**](/docs/on-premises/10.x/architecture/metoro-exporter/components/opentelemetry-collector) scrapes Prometheus-compatible targets and forwards metrics through the exporter. [**Target Allocator**](/docs/on-premises/10.x/architecture/metoro-exporter/components/target-allocator) watches ServiceMonitor and PodMonitor resources and assigns scrape targets to collector replicas. [**Redis**](/docs/on-premises/10.x/architecture/metoro-exporter/components/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](/docs/on-premises/10.x/architecture/metoro-hub/overview).