open-telemetry/opentelemetry-collector

Health v2 · maintenance only

Adoption not part of the score

7455 stars · 2215 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

The OpenTelemetry Collector is a vendor-agnostic telemetry pipeline service that receives, processes, and exports traces, metrics, and logs to any observability backend. It replaces the need to run multiple agents/collectors by supporting open-source telemetry formats like Jaeger and Prometheus through a configurable pipeline of 200+ components.

Use cases

• collect and forward traces metrics and logs to any observability backend
• replace multiple vendor telemetry agents with a single collector
• process filter and route telemetry data in a pipeline
• deploy a telemetry gateway or sidecar agent for kubernetes clusters
• convert prometheus and jaeger data to otlp
• tail and parse log files and ship them to a backend
• avoid vendor lock-in for observability data

When to choose

• you need a vendor-neutral way to receive, process, and export telemetry data
• you want one agent to support multiple telemetry formats and backends
• you need to route, filter, or transform traces, metrics, and logs at scale
• you are standardizing on OpenTelemetry across a cloud-native infrastructure

When to avoid

• you need a full observability backend with storage and visualization - the Collector is not a backend
• you only need application-level instrumentation APIs and SDKs rather than a collection pipeline
• you want a lightweight single-purpose agent with no configuration surface

Facets

service · maturity stable

monitoring tracing logging middleware monitoring cloud-computing microservices go cross-platform self-hosted cloud opentelemetry telemetry otel-collector vendor-neutral otlp observability-agent traces metrics-pipeline devops docker kubernetes

Member repositories

For agents

markdown · JSON · MCP: product_card(name="open-telemetry/opentelemetry-collector")