🔎
🩺 Check
LV2 · Toolooo Standard
Explore → See → Understand → ActUnderstand it. Feature Level describes the depth of the tool experience.

OpenTelemetry Trace Doctor

Check trace structure, timing, service identity and sensitive-data signals in static OTLP JSON.

EngineeringBackendAPISecurityPerformanceAI
🔒Your tool inputs are processed in your browser and are not uploaded or sent to analytics.

Is your trace connected, useful and safe to collect? Paste a static JSON sample, inspect the main issue, then fix the instrumentation. No collector is contacted.

200,000 UTF-8 bytes · 200 spans · 24 levels · 100 attributes per span · 2,000 total attributes · 1,000 events · 150 findings. Paste stays visible in this editor and in page memory only. Findings omit attribute values; operation/service labels are filtered, not guaranteed anonymization. Redact real data before pasting.
Try a synthetic sample
Formats, assumptions and limits

Supports OTLP resourceSpans/scopeSpans (including instrumentationLibrarySpans), span arrays, a spans wrapper, and single spans. Simplified examples accept resource attribute objects and trace_id/span_id aliases. Use decimal-string Unix nanoseconds, explicit Unix milliseconds, or offset ISO startTime/endTime. Ambiguous numeric timestamps are not guessed. IDs use nonzero hex, not base64.

Structure failures are distinct from partial-sample gaps. Multiple roots do not automatically fail. Resource identity, naming, privacy, uniqueness and long-duration checks are diagnostic guidance, not certification. Service namespace, instance and version are optional. Selected convention type checks do not validate every protocol or vendor. GenAI content is never required. No full prompts, raw bodies or stack traces are needed. Nothing is copied, exported, stored or included in shared links by this tool.

OTLP JSON specification · Service identity · HTTP conventions · GenAI conventions and content disclosure

What this tool does and why

Before you start

What

Check trace structure, timing, service identity and sensitive-data signals in static OTLP JSON.

Why

Connected spans need useful service identity and bounded, safe attributes. Partial exports and evolving conventions require context rather than blanket compliance claims.

Your Result and Action update in the tool as you change its inputs.

Model note

This browser-side model explains the inputs you choose. Check an important decision against the real system, brief, or production constraints.

Next

Use the result to choose a connected next move.

Network Failure UX SimulatorCompare seeded retry strategies, waiting, failures and recovery from the frontend user’s perspective.AI Agent Cost & Loop SimulatorCompare agent token, retry, branch and model-cost growth against explicit guardrails using your own prices.
How this tool stays honest

How it works

Paste a bounded OpenTelemetry JSON sample and inspect parent relationships, timestamp safety, naming, selected semantic-convention types, error context and GenAI content disclosure. Review masked evidence and prioritized fixes without uploading telemetry or connecting a collector.

Assumptions

The tool runs in your browser and models the information you provide. It does not know facts outside that model.

Limitations

Bounded static OTLP JSON review, not collector validation, runtime tracing, complete semantic-convention compliance or security certification. Partial samples, clock skew and instrumentation versions need context. Heuristic masking is not guaranteed anonymization; redact real data first.

Understand OpenTelemetry Trace Doctor

What this tool helps you understand

Paste a bounded OpenTelemetry JSON sample and inspect parent relationships, timestamp safety, naming, selected semantic-convention types, error context and GenAI content disclosure. Review masked evidence and prioritized fixes without uploading telemetry or connecting a collector.

When to use it

Before collecting or sharing a trace export, or when parent relationships look broken.

Try a scenario

Load Healthy Web Trace, then Broken Parent Trace. Compare a missing parent warning with definite ID errors; use the synthetic Privacy Leak sample to inspect masked findings.

How to read the result

Fix definite structure/time errors first, then review privacy and identity signals. Missing parents and multiple roots may reflect a partial sample. PASS only covers supported checks.

Assumptions and limits

Bounded static OTLP JSON review, not collector validation, runtime tracing, complete semantic-convention compliance or security certification. Partial samples, clock skew and instrumentation versions need context. Heuristic masking is not guaranteed anonymization; redact real data first.

Toolooo is part of Khizooology, created byKhizar Imtiaz (khizooo).