$ show open-telemetry/opentelemetry-collector-contrib
This is the OpenTelemetry Collector Contrib repository, a large monorepo of optional components extending the OpenTelemetry Collector. It provides receivers, processors, exporters, extensions, and connectors for collecting, processing, and exporting telemetry data (traces, metrics, logs, profiles). The codebase is written in Go and follows a consistent component factory pattern with metadata-driven code generation. It integrates with dozens of external systems (AWS, Azure, GCP, Kafka, Elasticsearch, Prometheus, Kubernetes, databases, etc.) and includes a domain-specific transformation language (OTTL) and a log pipeline framework (Stanza). The architecture is modular, with each component self-contained in its own package. The repository is actively maintained with frequent commits, extensive CI, and a well-structured build system.
The LLM identified 4 files worth highlighting for reuse:
A Go library implementing the OpenTelemetry Transformation Language (OTTL) for manipulating telemetry data. It provides contexts for spans, logs, metrics, and profiles, along with a rich set of functions for string manipulation, hashing, type conversion, and conditional logic. The parser and evaluator are designed to be extensible and can be reused in any Go project requiring structured data transformation, not just the OpenTelemetry Collector.
A generic, lock-free LRU set implementation optimized for high-throughput use. It uses an internal doubly-linked list and map for O(1) operations, with support for custom eviction callbacks. This is a self-contained, well-tested data structure that can be extracted and reused in any Go application needing an evictable set with a fixed capacity, such as deduplication or caching.
A configurable failover connector that routes telemetry data across multiple downstream pipelines with automatic fallback. It implements a state machine for pipeline selection (including cool-down periods and conditions-based retry), and handles all three signal types (logs, metrics, traces). The pattern is generic enough to be adapted to any streaming or RPC system requiring seamless failover between endpoints.
A composable operator framework for building log processing pipelines. It defines a registry pattern for input, parser, transformer, and output operators, each with a consistent lifecycle (Start, Process, Stop). The framework supports JSON, regex, key-value, syslog, and many other parsers, and can be extended with custom operators. The core abstractions are decoupled from the OpenTelemetry Collector and could be used as a standalone log processing library.