Local OTLP Trace Timing Review

How to use Local OTLP Trace Timing Review

Inspect actual supplied OTLP JSON spans with exact nanosecond timing, parent evidence and union-clipped child intervals. Review a small offline trace export without a collector or backend. Exact timestamp strings preserve nanoseconds beyond JavaScript integer precision; parent cycles, missing parents and children outside parent intervals remain source diagnostics instead of silently becoming performance conclusions.

1. Provide optional otlp trace json file, one otlp resourcespans json envelope.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• One UTF-8 JSON object up to 200,000 bytes, 10,000 values and 40 levels. Select resourceSpans/scopeSpans/spans in lowerCamelCase: at most 100 resource groups, 200 aggregate scope groups, 500 spans and 100 distinct traces. No NDJSON, protobuf binary, compressed input, metrics or logs envelope is imported.
• Each selected span has a nonblank name up to 200 UTF-8 bytes, complete nonzero 32-hex traceId and 16-hex spanId, and optional empty or complete parentSpanId. Hex is case-insensitive and canonicalized to lowercase. Repeated traceId/spanId pairs are refused as ambiguous.
• startTimeUnixNano and endTimeUnixNano must be canonical decimal uint64 strings, 0–18,446,744,073,709,551,615. This intentionally narrower export profile refuses numeric JSON timestamp spellings and exponents instead of rounding them. End-before-start is reported without a valid duration.
• For each valid span, direct-child intervals are clipped to the parent and unioned before subtraction. Overlapping children are counted once. A parent-cycle path has no exclusive value; a missing parent is outside this selection. Partial traces, clock skew and asynchronous instrumentation can make selected exclusive time differ from actual application self time.
• Trace envelope length and sum of selected span durations are separate exact values; duration sums can double-count parallel/nested work. No critical path, cross-machine clock correction, request percentile, flame graph, complete OTLP schema validation or server-observed latency is claimed.
• Only literal resource service.name is selected from attributes, at most one per resource and 200 bytes. Other attributes/events/links/kind/status/unknown fields are neither validated nor returned. Span/service names and IDs can still be private; this report is not automatic anonymization.
• The same-origin Worker prepares within 10 seconds, then computes under a separate 2-second deadline. Report text is capped at 500,000 characters. No collector, URL, service, file path or credential is contacted, and no trace data is uploaded or persisted automatically.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.