Module otlp 

OpenTelemetry HTTP/gRPC receiver — the model decides which exports are accepted.

OTLP exporters POST to /v1/traces, /v1/metrics or /v1/logs in protobuf or JSON, optionally gzip-compressed. NetGet reads the body (bounded before and after inflation), decodes it, and raises one otlp_export event carrying a summary — never the payload. The model answers with a verdict (accept_otlp, accept_otlp_partially, reject_otlp), and NetGet encodes the response in the request’s own encoding (see codec). Generated unary gRPC Export services use the same semantic verdict path on HTTP/2.

Everything that is not a well-formed export is answered by NetGet without asking the model: another path (404), method (405), content type or content encoding (415), a body past the cap (413), bad gzip or an undecodable payload (400).

See src/server/otlp/AGENTS.md.

Re-exports

pub use codec::MAX_BODY_BYTES;

Modules

actions

OTLP actions: what the model is told about an export, and how its verdict becomes a response.

codec

OTLP/HTTP payloads: decoding an export request into the summary the model sees, and encoding every response the receiver sends.

Structs

OtlpServer

OTLP/HTTP receiver.