OpenTelemetry Collector
The OpenTelemetry Collector is a vendor-neutral service that receives, processes, and exports telemetry data.
Cloud Observability in Action
The OpenTelemetry Collector is a vendor-neutral service for receiving, processing, and exporting telemetry data.
- How it is used
- Routes correlated logs, metrics, and traces between heterogeneous sources and backend destinations in vendor-neutral observability deployments.
- How deep it goes
- Explains pipeline components, OTLP delivery, configuration examples, and profiling, but stops short of detailed collector internals.
- Examples
- Demonstrates Docker Compose pipelines sending metrics to Prometheus, traces to Jaeger, and profiles to Parca.
- What you can do after
- Operate/configure a collector with receivers, processors, exporters, OTLP, Docker Compose, Prometheus, Jaeger, and pprof.
Read how Cloud Observability in Action explains OpenTelemetry Collector →
Logs and Telemetry
The OpenTelemetry Collector is a vendor-neutral service component that receives, processes, and exports telemetry data.
- How it is used
- Connects application telemetry producers with OTLP-compatible aggregation, processing, and analysis services.
- How deep it goes
- Defines collector and exporter roles and clarifies terminology, but stops short of configuration or implementation mechanics.
- Examples
- Illustrates applications sending telemetry through Fluent Bit to an OpenTelemetry-compliant aggregation or analysis service.
- What you can do after
- Evaluate whether Fluent Bit or another OTLP-compatible component can collect, transform, and forward application telemetry.
Read how Logs and Telemetry explains OpenTelemetry Collector →
gRPC Microservices in Go
The OpenTelemetry Collector is a vendor-neutral service that receives, processes, and exports observability telemetry.
- How it is used
- Connects gRPC microservices with Jaeger and Prometheus in a Kubernetes observability deployment.
- How deep it goes
- Explains deployment ports and service instrumentation, then stops short of detailed collector pipeline configuration.
- Examples
- Uses Helm deployment commands, collector service URLs, Jaeger UI access, and Order-to-Payment trace propagation.
- What you can do after
- Operate/configure a Kubernetes telemetry path and instrument Go gRPC services to export traces and metrics.
Read how gRPC Microservices in Go explains OpenTelemetry Collector →
Related concepts
- Jaegeruses · Jaeger is an open-source distributed tracing system for collecting, storing, querying, and visualizing trace data to monitor and troubleshoot distributed applications.
- pipelinehas part · A pipeline is an ordered or coordinated sequence of connected processing stages or tasks that passes data, work, or results toward an outcome.
- pprofconfigured by · pprof is Go’s profiling toolset and package ecosystem for collecting, analyzing, and visualizing runtime performance profiles.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.