liveBook · Manning

gRPC

As explained in Logs and Telemetry

gRPC is a high-performance remote procedure call framework that commonly uses HTTP/2 and Protocol Buffers for communication.

gRPC is a high-performance remote procedure call framework used to transmit OpenTelemetry data. Within OTLP, it commonly operates synchronously over HTTP/2 with Protocol Buffers; JSON provides a fallback path. section 1.3.2

Operationally, gRPC provides:

  • A first-choice communication method for OTLP telemetry. section 1.3.2
  • A way for applications and OpenTelemetry-compatible collectors to exchange telemetry through distributed pipelines. section 1.3.2
Figure 1.3 Fluent Bit’s relationship with OpenTelemetry with apps generating OTel logs, metrics, and traces and Fluent Bit facilitating their transmission to an OTel-compliant point of aggregation or processing. Applications can send OTLP data directly or via an OTel component, and we can route data to other OTel services or analysis tools.
figure

The diagram traces applications generating logs, metrics, and traces through Fluent Bit or other OpenTelemetry components toward aggregation, processing, and analysis services. section 1.3.2

How Logs and Telemetry covers it

How deep it goes
Explains transport formats and ecosystem placement but does not descend into RPC service implementation.
Examples
Shows telemetry flowing from applications through Fluent Bit or another OpenTelemetry component to compliant services.
What you can do after
Evaluate gRPC as the preferred OTLP transport and recognize JSON as its fallback alternative.
How it connects
Connects gRPC with OpenTelemetry Protocol, HTTP/2, Protocol Buffers, JSON, and OpenTelemetry Collector architectures.

Also explained in

Compare how 10 books explain gRPC →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Logs and Telemetry. The section links point to the parts of the book it draws on.