Skip to content

OTLP Inspector

Inspect OTLP traces, metrics, and logs from JSON, raw Protobuf, gRPC frames, and GZIP-compressed payloads locally.

OTLP workspace

Inspect schema-backed OTLP export requests locally. No collector or network connection is used.

Input format

Add an OTLP export request

Choose its signal and transport, then inspect JSON or bytes.

Did DecodeLens help?

Support the continued development of independent, browser-local developer tools.

Schema-backed OTLP inspection

DecodeLens uses its reviewed OpenTelemetry v1.11.0 schema projection and bounded workers. It does not infer arbitrary Protobuf as OTLP.

Inspection boundaries

  • Supports stable trace, metric, and log export requests; development profiles are excluded.
  • Binary inputs require an explicit signal; transport and compression selections must match the supplied bytes.
  • The trace waterfall is bounded and is an inspection aid, not a distributed tracing backend.
  • No collector connection, remote lookup, telemetry upload, or browser persistence occurs.

Continue with tools that decode, convert, inspect, or verify the same data.

Inspect an OpenTelemetry export request

Select the signal and exact transport, supply the payload, and review resources, instrumentation scopes, records, findings, and trace timing without contacting a collector.

Example input

{ "resourceSpans": [{ "scopeSpans": [{ "spans": [{ "name": "GET /health" }] }] }] }

Inspector output

1 resource · 1 scope · 1 span
service, schema, findings, record details, trace waterfall

OTLP Inspector FAQ

Does this send telemetry to a collector?

No. Payloads are decoded locally in bounded browser workers and are not uploaded or persisted.

Which OTLP encodings are supported?

Stable traces, metrics, and logs in OTLP JSON, raw Protobuf, gRPC frames, and optional GZIP compression.

Does it guess unknown Protobuf schemas?

No. Binary meaning comes only from the reviewed OTLP v1.11.0 descriptor projection and explicit signal selection.