Log & Incident Explorer
Data & analysis Local only
OpenTelemetry Trace Explorer
Local trace analysisExplore OTLP, Jaeger, and Zipkin traces as waterfalls, service edges, diagnostics, and comparisons.
How to use it
- 01
Import trace evidence
Open OTLP JSON, Jaeger JSON, Zipkin v2 JSON, or a gzip-compressed JSON capture in the browser.
- 02
Follow the trace
Select a trace, filter spans, inspect parent-child timing, status, attributes, events and links, and highlight the longest ending chain.
- 03
Diagnose systems
Review service-to-service edges, latency percentiles, errors and malformed identifiers, compare two datasets, and export a redacted report.
Frequently asked questions
Does this tool receive OTLP over HTTP or gRPC?
No. A static page has no collector endpoint. Export OTLP JSON or supported backend JSON and open the file locally.
Which formats are supported?
The importer recognizes OTLP JSON resourceSpans, Jaeger JSON data arrays, and Zipkin v2 JSON span arrays, plus gzip-wrapped JSON where the browser supports decompression streams.
Is the highlighted chain a full critical-path proof?
No. It follows the child that ends latest at each level as a useful latency lead. Asynchronous work, missing spans, clock skew, and links can change the real causal path.
Are span attributes safe to share?
Not automatically. The report redacts common secret-like keys, but telemetry can contain customer data or identifiers under custom names, so review exports before sharing.
Related tools
Keep working with other focused browser utilities.