OpenTelemetry Collector
An open-source data collector from the OpenTelemetry project that receives, processes and forwards telemetry data, supporting a range of data sources and export targets.
Timeline (last 90 days)
Nike's closed-loop system flow is: the agent observes the telemetry backend and fleet status through MCP read-only tools, drafts a configuration change proposal, and after human approval the OpAMP server delivers it to the Collectors, then decides on full rollout or rollback based on validation results.
Nike manages about 100,000 OpenTelemetry Collectors during major promotions, with a very small team.
OpenTelemetry Collector is a vendor-neutral telemetry data collector under the CNCF that supports receiving, processing and exporting metrics, logs and trace data.
The Collector has both the gRPC (4317) and HTTP (4318) receivers enabled, and on the Claude Code side gRPC transport can be selected via OTEL_EXPORTER_OTLP_PROTOCOL=grpc.
In the local observability stack, the OpenTelemetry Collector exposes metrics in Prometheus format on port 8889, Prometheus scrapes at 15-second intervals, and Grafana reads the Prometheus data source.
In production environments, an OpenTelemetry Collector typically receives OTLP data and then routes it to different backends according to configuration, so the application side only needs to program against OTLP and need not be tied to a specific vendor.
Creating a separate span for each token chunk of a streaming response leads to span explosion; for example, a response generating 1,500 tokens would produce 1,500 spans, potentially overwhelming the memory buffer and causing the Collector to crash.
The OpenTelemetry Collector adopts a pipeline architecture composed of three major modules: Receiver, Processor, and Exporter.
All Facts (8)
Nike's closed-loop system flow is: the agent observes the telemetry backend and fleet status through MCP read-only tools, drafts a configuration change proposal, and after human approval the OpAMP server delivers it to the Collectors, then decides on full rollout or rollback based on validation results.
50%UnverifiedNike manages about 100,000 OpenTelemetry Collectors during major promotions, with a very small team.
50%UnverifiedOpenTelemetry Collector is a vendor-neutral telemetry data collector under the CNCF that supports receiving, processing and exporting metrics, logs and trace data.
50%UnverifiedThe Collector has both the gRPC (4317) and HTTP (4318) receivers enabled, and on the Claude Code side gRPC transport can be selected via OTEL_EXPORTER_OTLP_PROTOCOL=grpc.
50%UnverifiedIn the local observability stack, the OpenTelemetry Collector exposes metrics in Prometheus format on port 8889, Prometheus scrapes at 15-second intervals, and Grafana reads the Prometheus data source.
50%UnverifiedIn production environments, an OpenTelemetry Collector typically receives OTLP data and then routes it to different backends according to configuration, so the application side only needs to program against OTLP and need not be tied to a specific vendor.
50%UnverifiedCreating a separate span for each token chunk of a streaming response leads to span explosion; for example, a response generating 1,500 tokens would produce 1,500 spans, potentially overwhelming the memory buffer and causing the Collector to crash.
50%UnverifiedThe OpenTelemetry Collector adopts a pipeline architecture composed of three major modules: Receiver, Processor, and Exporter.
50%