Traceplain
FREE OTLP JSON VIEWER · NO ACCOUNT

Turn a GenAI trace into a human review.

Import OpenTelemetry OTLP JSON locally and review recorded agent operations, tool calls, status, timing, service context, and what the trace still cannot prove.

Try the safe OTLP sample Download safe sample

Imported trace data never leaves your browser.

1. Obtain an OTLP JSON trace.

Export or download one traces payload from your OpenTelemetry collector, file exporter, or observability backend. Traceplain reads the standard nested shape:

resourceSpans → scopeSpans → spans
span → traceId, spanId, name, attributes, status, timestamps

OTLP JSON uses lower-camel-case field names and numeric enum values. Traceplain accepts the trace export itself; it is not an OTLP network receiver and does not require a collector connection.

2. Inspect sensitive content before sharing.

GenAI semantic attributes can contain prompts, completions, tool arguments, tool results, conversation identifiers, and other project context. Keep the original file local unless you have authority to share it. Traceplain processes it in your browser and does not transmit imported content.

3. Read status conservatively.

HOW TRACEPLAIN TREATS OTLP SPANS
  • status.code: 1 is shown as a recorded OK result;
  • status.code: 2 is shown as a recorded error;
  • unset status stays unknown and is never silently promoted to success;
  • gen_ai.tool.name, operation, model, service, timing, and trace identity remain distinct evidence;
  • a recorded span supports only what that instrumentation captured.
OBSERVED       search_knowledge_base · OK · 220 ms
OBSERVED       update_ticket · ERROR · permission denied
UNKNOWN        whether an uninstrumented side effect occurred
NEEDS HUMAN    verify the ticket state in its system of record

Supported trace evidence.

  • OTLP JSON resourceSpans, scopeSpans, and spans;
  • resource service name and instrumentation scope;
  • GenAI operation, agent, model, tool name, and tool-call arguments;
  • span status, status message, start/end timing, trace ID, and span ID;
  • nested OTLP scalar, array, and key-value-list attributes.

Traceplain does not establish trace completeness, recompute backend sampling decisions, or prove real-world outcomes outside the supplied telemetry.

QUICK ANSWERS

OpenTelemetry GenAI viewer FAQ

What file format should I use?

Use an OTLP JSON traces payload containing resourceSpans. The downloadable synthetic sample shows the accepted shape.

Does Traceplain send the trace anywhere?

No. Imported content is parsed locally. Aggregate counters contain no trace attributes, prompts, tool arguments, or identifiers.

Does an OK span prove the agent succeeded?

No. It records the instrumentation’s status for that operation. The intended real-world outcome may still need an independent check.

Is Traceplain an OpenTelemetry backend?

No. It is a local human-review surface for an exported trace, not a collector, storage service, or live observability platform.