open-telemetry / opentelemetry-collector Architecture and code health
OpenTelemetry Collector
Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.
Releases on GitHub (latest v0.165.0, Nov 6, 2026)
Repowise maps public repos from their source. Not affiliated with open-telemetry. What is Repowise?
github.com/open-telemetry/opentelemetry-collectorIndexed at a5a8fef
What is opentelemetry-collector?
opentelemetry-collector is a vendor-agnostic service that receives telemetry data such as traces, metrics, logs and profiles, processes it, and exports it to one or more back-ends. It lets operators avoid running a separate agent for each telemetry format and destination, including open formats such as Jaeger and Prometheus. The project is written in Go. Its code health is 8.6 out of 10 (Excellent), ranked #35 of 4,000+ indexed repos. The last commit to opentelemetry-collector was on Oct 27, 2026, and 93 people have contributed.
As of commit a5a8fef, indexed Oct 27, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.
For agentsopentelemetry-collector.md
Repo facts: type, license, health, rank, contributors
| License | Apache-2.0 |
|---|---|
| Code health | 8.6 / 10 (Excellent) |
| Health rank | #35 of 4,000+ indexed repos |
| Last commit | Oct 27, 2026 |
| Contributors | 93 |
| Bus factor | 1 |
| Size | 2,311 files, 195,859 lines |
Explore opentelemetry-collector
- DocumentationModule-by-module documentation, 1,912 pages.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score and the findings behind it.
- CommitsEach commit's effect on code health.
- OverviewEverything else the index found: contributors, decisions, what changed this week.
Ask about this code in your agent
This connects Repowise to opentelemetry-collector's code. It does not install opentelemetry-collector.
Useful if you want to change or fork opentelemetry-collector: your agent can ask how it is put together and get answers that cite its files.
Ask about opentelemetry-collector
Answers come from opentelemetry-collector's README and source, with the files they cite. Two free answers a day without an account.
Want this for your own codebase? Map your repo free
About this page
Get a page like this for your own codebase
Repowise built this map of open-telemetry/opentelemetry-collector from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.
Free for 2 public repos, with a page like this one. No card. See how Repowise works
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub
open-telemetry/opentelemetry-collector FAQ
What is opentelemetry-collector?
opentelemetry-collector is a vendor-agnostic service that receives, processes and exports telemetry data such as traces, metrics, logs and profiles. It removes the need to run and maintain separate agents for each open telemetry format and back-end.
How does opentelemetry-collector work?
opentelemetry-collector receives telemetry through receiver endpoints and passes it through a configured graph of processors, connectors and exporters. Its configuration is merged from layered YAML sources. Telemetry is then delivered to one or more back-ends.
What language is opentelemetry-collector written in?
opentelemetry-collector is written in Go, with Makefile and shell files used for build and tooling.
How is the opentelemetry-collector code organized?
opentelemetry-collector is organized into 21 Go modules, including pdata, exporter, service, cmd and confmap. The cmd directory holds three command-line tools: two generate Go code from declarative files and one builds a custom collector binary.
When should I use opentelemetry-collector?
Use opentelemetry-collector when you need to receive, process and export telemetry from open formats such as Jaeger and Prometheus to several open-source or commercial back-ends. It lets you do this without running multiple agents or collectors.
What license does opentelemetry-collector use?
opentelemetry-collector is licensed under Apache-2.0.
Code health
Hotspots average 5.6, the place fixes pay off most.
On the leaderboards:#1 of 28 Go repos
Key features of opentelemetry-collector
- Receives, processes and exports telemetry data in a vendor-agnostic way.
- Supports popular protocols and runs with a reasonable default configuration.
- Can be extended with custom components without changing the core code.
- Runs as an agent or a collector from a single codebase, with support for traces, metrics and logs.
How open-telemetry/opentelemetry-collector works
Telemetry enters through receiver endpoints, and configuration is loaded from layered YAML files. The confmap package merges the configured locations into one configuration by asking a registered provider to fetch each one and then expanding references in the result. The component package defines what a component must do to start and stop and what it can ask of its host. The connector package passes telemetry of one signal type to downstream consumers, which may belong to a pipeline of another signal type. The pdata package holds the shared in-memory data model that telemetry is kept in as it moves through the pipeline. The cmd/builder/main.go entry point builds a custom collector binary, while cmd/mdatagen and cmd/schemagen generate Go code from declarative files.
The codebase has 2,311 files and 13,821 symbols in 21 modules, led by Go, Makefile and Shell. Code health is 8.5 out of 10, rated excellent.
Maintain open-telemetry/opentelemetry-collector?
Claim this page, add a badge to the README, or re-index it.
Claim this page
Sign in with GitHub and we check that you are an admin or maintainer of open-telemetry/opentelemetry-collector. Then add a badge to the README that links readers here.
Add a badge to your README
Readers click through to this page and can ask opentelemetry-collector's code a question. A badge also re-indexes the repo every week and marks you as the verified maintainer.
[](https://repowise.dev/repo/open-telemetry/opentelemetry-collector?src=badge_ask)Paste it at the top of README.md, under the title.
Added it already? Verify to get the mark now instead of tomorrow.
Need HTML or the larger health card? More formatsHide more formats
This badge as HTML
<a href="https://repowise.dev/repo/open-telemetry/opentelemetry-collector?src=badge_ask"><img src="https://api.repowise.dev/badge/wiki/open-telemetry/opentelemetry-collector.svg?label=ask" alt="repowise: Ask this codebase"></a>Code health card
The score, its change since the last index, and when it was measured. Follows the reader's light or dark theme.
<a href="https://repowise.dev/repo/open-telemetry/opentelemetry-collector?src=badge_card"><picture><source media="(prefers-color-scheme: light)" srcset="https://api.repowise.dev/badge/health/open-telemetry/opentelemetry-collector.svg?style=card&theme=light"><img src="https://api.repowise.dev/badge/health/open-telemetry/opentelemetry-collector.svg?style=card" alt="repowise code health" width="500" height="168"></picture></a>