DiagramPreview
Vista avanzadaLive previewExportDeveloper tool

OpenTelemetry Trace to Sequence

Convert OpenTelemetry spans JSON into a Mermaid sequence diagram for request flow review.

Ejemplos
Detected JSON

This input may work better in the matching tool. Open JSON tool

Rendered previewListo
The preview will appear here.

Continue with a related tool

Move this preview into a nearby workflow for conversion, debugging, or export.

Cómo usar

  1. 1Paste source or load a sample.
  2. 2Review the rendered preview or structured output.
  3. 3Copy code, export images, or download generated files.

Casos de uso

AI-generated diagram validationDeveloper docs and README workflowsArchitecture, monitoring, and config review

FAQ

What is OpenTelemetry Trace to Sequence for?

Convert OpenTelemetry spans JSON into a Mermaid sequence diagram for request flow review.

Does it require an account?

No. The tool page can be used directly in the browser.

OpenTelemetry Trace to Sequence is designed for developer documentation, AI-generated diagram validation, and engineering configuration visualization.

It helps convert source text, config, or AI output into a previewable and exportable result.

Demo: convert spans into a request sequence

OpenTelemetry traces already contain timing and parent-child relationships. A sequence preview makes it easier to explain a slow request across gateway, service, database, and queue boundaries.

  • Preserve service.name and span.name as participant and message labels.
  • Use timestamps to order sibling spans when possible.
  • Highlight long spans instead of showing every tiny internal operation.
[{"traceId":"t1","spanId":"1","name":"POST /checkout","service.name":"gateway"},{"spanId":"2","parentSpanId":"1","name":"SELECT inventory","service.name":"inventory"}]

Incident review: traces need context

A trace diagram helps tell the story of one request. For incident work, compare it with logs, metrics, and deployment changes so one slow trace is not over-generalized.

  • Use one normal trace and one slow trace for comparison.
  • Collapse low-value internal spans to keep the sequence readable.
  • Remove sensitive attributes before sharing trace JSON.
normal p95 trace -> 280ms
incident trace -> inventory SELECT 2300ms

Checklist de revisión para OpenTelemetry Trace to Sequence

Usa OpenTelemetry Trace to Sequence para inspeccionar visualmente contenido fuente antes de publicar documentación, notas de PR, incidentes o handoffs. Convert OpenTelemetry spans JSON into a Mermaid sequence diagram for request flow review.

Antes de exportar, revisa legibilidad, relaciones, datos sensibles y si la vista sigue teniendo sentido tras editar la entrada.

Límites y solución de problemas

Si la vista falla, reduce la entrada al ejemplo completo más pequeño, valida la sintaxis y agrega secciones gradualmente.

Trata la vista como superficie de revisión, no como fuente de verdad. Los resultados críticos requieren validación humana.

Entradas de ejemplo

  • Checkout: { "spans": [ { "name": "POST /checkout", "serviceName": "api", "parentService": "client" }, { "name": "Reserve inventory", "serviceName": "inventory", "parentService": "api" }, { "...
  • Login: { "spans": [ { "name": "POST /login", "serviceName": "web", "parentService": "client" }, { "name": "Validate token", "serviceName": "auth", "parentService": "web" } ] }
  • Queue: { "spans": [ { "name": "Publish event", "serviceName": "api", "parentService": "client" }, { "name": "Consume event", "serviceName": "worker", "parentService": "api" } ] }

Madurez de la herramienta

Vista avanzada

Analizador avanzado

Esta herramienta extrae estructura y relaciones de entradas de desarrollo. Los casos complejos deben comprobarse contra la fuente.

La etiqueta indica si la herramienta sirve mejor para exportar, depurar, analizar rápido o generar con AI.