OpenTelemetry Collector
apartment
4 companies hiring
Radar: Initial
Apache-2.0
Receives, processes and exports telemetry in a vendor-agnostic pipeline — the component that decouples what emits telemetry from what stores it.
OpenTelemetry / OTLP
Specifications it implements
What this tool does to each specification, in the role vocabulary. Follow a standard through to standards.apievangelist.com for what it actually specifies.
| Standard | Role | What that means |
|---|---|---|
| OpenTelemetry / OTLP | instrumentsalso transforms |
Using this from an agent
- Interfaces
containercli- Invoke
otelcol --config <config.yaml>- Consumes
- otlp, prometheus, jaeger, zipkin
- Emits
- otlp
- Runtime
- Runs offline Non-deterministic Read-only Needs credentials
Where it applies
Jobs this tool actually does, and the surface each one is exercised on.
Change observability backends without touching a line of application code.
coding-agentci-pipeline
The architectural reason OTLP matters. Instrument once against the standard, and the destination becomes a configuration decision rather than a migration.
Redact or drop sensitive attributes in telemetry before it leaves the estate.
ci-pipeline
- Website
- https://opentelemetry.io
- Repository
- https://github.com/open-telemetry/opentelemetry-collector
- License
- Apache-2.0 — reported by the GitHub API, verified 2026-09-17
- Stars
- 7563 · last commit 2026-09-17
- Companies hiring
- 4 — distinct companies whose job postings name this tool, Q3-2026. A demand signal, not a deployment count.
Reading this as an agent? Don't scrape the page — this entry is published as
structured data at
arrow_back
All tools by adoption
/tools.json,
against the tool.schema.json
schema, using the roles.json
vocabulary. Start at /llms.txt.