Skip to main content
OpenTelemetry Collector handles Prometheus-compatible metric scraping for the exporter chart. It receives scrape assignments from the target allocator, scrapes configured targets, batches metrics, and forwards them to Metoro Exporter.

​
Talks To

​
How It Fits

The collector is used when ServiceMonitor scraping is enabled. It runs with a collector configuration generated by the chart and uses the target allocator endpoint to learn which Prometheus scrape targets belong to each collector replica. After scraping, the collector sends metrics to Metoro Exporter through the cluster-local exporter service. Metoro Exporter then forwards those metrics through the hub ingestion path. The chart deploys the collector as a StatefulSet so each collector replica has a stable identity for target allocation. The collector does not own durable telemetry state; its role is to scrape, batch, and forward.

​
Operational Notes

Collector replica count controls ServiceMonitor scrape capacity. If scrape volume grows, operators can increase collector replicas and let the target allocator rebalance assignments. Collector health is most visible in missing or delayed scraped metrics. If node-agent telemetry is healthy but Prometheus-style metrics are incomplete, inspect the collector, target allocator, and scrape target configuration together.