liveBook · Manning

Receiver

As explained in Cloud Observability in Action

An OpenTelemetry receiver is a Collector component that accepts telemetry from an external source or protocol.

An OpenTelemetry receiver is a Collector component that accepts telemetry from an external source or protocol and starts its path through a pipeline. section 4.3.2

Receivers participate in telemetry workflows by:

  • Accepting signals such as metrics or traces from sources. section 4.3.2
  • Supporting protocol-specific configurations, such as OTLP over gRPC or Prometheus scraping. section 4.3.2
  • Connecting independently defined pipelines to processors and exporters. section 4.3.2

Metrics and traces in one Collector

A Collector can use a Prometheus receiver for metrics and an OTLP receiver for traces. Separate pipelines batch and export those signals to Prometheus and Jaeger.

How Cloud Observability in Action covers it

How deep it goes
Defines the pipeline role and shows configuration, but stops short of receiver implementation internals.
Examples
Uses OTLP over gRPC for traces and Prometheus scraping for metrics in a Docker Compose observability stack.
What it assumes
Assumes familiarity with telemetry signals and Collector pipelines while establishing receivers as pipeline inputs.
What you can do after
Configure it via named receiver types and attach it to signal-specific Collector pipelines.
How it connects
Connects receivers with Collector pipelines, processors, exporters, OTLP, metrics, traces, Prometheus, and Jaeger.
Cover of Cloud Observability in Action
liveBookmanning.com
Read Cloud Observability in Action on liveBook Get the book at manning.com

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Cloud Observability in Action. The section links point to the parts of the book it draws on.