DiagramPreview
Aperçu avancéLive previewExportDeveloper tool

OpenTelemetry Trace to Sequence

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

Exemples
Detected JSON

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

Rendered previewPrêt
The preview will appear here.

Continue with a related tool

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

Comment utiliser

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

Cas d’usage

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 revue pour OpenTelemetry Trace to Sequence

Utilisez OpenTelemetry Trace to Sequence pour inspecter visuellement une source avant documentation, note de PR, post-mortem ou transfert. Convert OpenTelemetry spans JSON into a Mermaid sequence diagram for request flow review.

Avant export, vérifiez la lisibilité, les relations, les données sensibles et la cohérence après modification.

Limites et dépannage

Si l'aperçu échoue, réduisez l'entrée au plus petit exemple complet, validez la syntaxe puis réajoutez les sections.

Considérez l'aperçu comme une surface de revue, pas comme une source de vérité. Les résultats critiques doivent être validés.

Exemples à tester

  • 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" } ] }

Maturité de l'outil

Aperçu avancé

Analyse avancée

Cet outil extrait la structure et les relations depuis des entrées développeur. Les cas complexes doivent être vérifiés avec la source.

Le libellé indique si l'outil convient surtout à l'export stable, au débogage, à l'analyse rapide ou à la génération AI.