Elysia Tools

Browse tools, examples, visual explainers, and topic guides from one clear workspace.

Top Categories

Hubs

Language
ZHDERUPTENFRES

Elysia Tools

Navigation

Workflow Playbook

Verify an OpenTelemetry Instrumentation Upgrade

Inventory old attributes, migrate OpenTelemetry conventions, validate propagation headers, and inspect a representative trace before releasing instrumentation changes.

This topic isn't available as a one-click template yet.Browse runnable topics →

Start here

New to this workflow? Follow the steps in order, starting with the first tool below. Already know what you need? Jump straight to the matching step — every tool in this workflow is listed in the comparison table.

First tool: Structured Log Analyzer

Hubs

Tools in this workflow, compared

ToolWhat it doesCategory
Structured Log AnalyzerDetect common log formats, extract core fields, infer field types, and export parsed logs as JSON, CSV, or SQL insertsData Processing
Logfmt to JSON Structured Log BridgeConvert logfmt (key=value) to JSON or JSON back to logfmt, with quote escaping, number/boolean coercion, and duplicate-key handling.Format Conversion
OpenTelemetry Semantic-Convention v1.20 → v1.27 Attribute Migration ToolRewrites span/log attribute names across OpenTelemetry semantic-convention versions: http.method → http.request.method, http.status_code → http.response.status_code, http.url → url.full, db.system → db.system.name, messaging.destination → messaging.destination.name and 25+ more — applied to pasted JS/TS/Python/Go/Java/.NET source, collector YAML or Grafana dashboard JSON, with an OTel Collector transform rename map, removal/manual-split warnings, per-attribute diff stats and an unmapped-attribute report.

Hubs

Continue with adjacent topic clusters

Development
OpenTelemetry W3C traceparent / tracestate / baggage + OTLP Header Propagation ValidatorValidate W3C Trace Context propagation headers end to end: traceparent (version / 16-byte trace-id / 8-byte parent-id / trace-flags), tracestate (≤32 list members, tenant keys), baggage (percent-encoded values + opaque properties), OTLP export Content-Type, the gRPC grpc-trace-context-bin 25-byte binary context — plus a two-header correlation round-trip with a random child span-id collision check.Development
Distributed Trace Decoder & Waterfall VisualizerDecode Jaeger, Zipkin, or OpenTelemetry trace JSON and render span timing, dependencies, and error hotspots as an interactive waterfall reportDevelopment
API Latency Budget PlannerPlan and visualise an API latency budget. Enter a P99 target (e.g. ≤ 300ms) and per-stage allocations (DNS, TCP, TLS, TTFB, Processing, Network) to see a live waterfall, budget utilisation, and over-budget warnings. Optionally paste an OpenTelemetry or Datadog trace to reverse-engineer a measured allocation.Development

Prepare a reproducible migration fixture

This playbook is for a service owner upgrading OpenTelemetry semantic conventions, not for an incident commander searching every available signal. Start with a sanitized before-change log, the current instrumentation or Collector snippet, a representative request that crosses at least two services, and the convention versions on both sides. Run structured-log-analyzer to identify fields already present. If the sample is logfmt, use logfmt-to-json-structured-log-bridge to expose quoted values, coercion and duplicate keys before comparing attributes; a JSON log does not need that detour. Remove personal or secret data before sharing fixtures. The pii-log-redaction workflow is the boundary for a full disclosure review.

Separate renameable fields from design changes

Run otel-semantic-convention-migration-tool on a copy of the relevant code, Collector configuration or dashboard JSON. Record the source and target version, proposed renames, removed attributes and anything unmapped. Its output is a proposed migration, not an automatic production deployment. A field such as http.target may require a deliberate split into path and query rather than a mechanical rename. Decide those cases with service owners, then deploy the reviewed change through the usual pipeline. Comparing only the count of renamed fields is not enough: a dashboard query or collector transform can still reference an old attribute.

Prove continuity with headers and a real export

Feed representative W3C traceparent, tracestate, baggage and OTLP export headers to opentelemetry-w3c-traceparent-tracestate-baggage-and-otlp-protobuf-headers-propagation-validator. Check that a downstream hop keeps the trace-id while using a different nonzero span-id. Valid headers do not prove that instrumentation actually emitted spans, so inspect a post-change JSON export with distributed-trace-decoder-waterfall-visualizer. Compare expected service hops, parent-child order, error spans and durations; write down any missing span rather than filling the gap with assumptions.

Tie the result to an explicit release gate

If the release has a latency objective, use api-latency-budget-planner to compare the observed stage durations with the pre-agreed allocations. A single trace suggests where time went, not a statistically valid P99. The acceptance note should contain the fixture version, attribute diff, header check, trace evidence, missing or unmapped fields, and any budget exception. If the original need is incident response or API payload replay rather than planned instrumentation migration, switch to observability-debugging or api-request-replay-and-debugging respectively.

Before you start

  • Capture a sanitized before-change log sample, one representative cross-service request trace, and the current instrumentation or collector configuration.
  • Identify the source and target semantic-convention versions; this migration tool supports the v1.20 to v1.23.1, v1.24 and v1.27 path.
  • Know the expected service hops, trace-id continuity, export format, and a separately agreed latency objective if performance is in scope.

Workflow playbook

OTel upgrade proof: inventory, migrate, propagate, inspect, budget

  1. 1

    Inventory representative log attributes

    Parse a sanitized before-change log sample. Convert logfmt to JSON only when needed so quoted values and duplicate keys are visible before the rename plan.

  2. 2

    Draft the convention migration

    Rewrite supported attributes from the selected v1.20 path, review the diff and collector rename map, and isolate removed or unmapped fields for manual decisions.

  3. 3

    Validate context and export headers

    Check sample traceparent, tracestate, baggage and OTLP headers across a representative hop, including trace-id continuity and child span-id changes.

  4. 4

    Inspect the exported trace

    Decode a post-change OTel, Jaeger or Zipkin JSON export and compare service order, span parents, errors and duration with the expected request path.

Choose the right path

Is the input logfmt or already structured JSON?

Convert logfmt first when quoting or duplicate keys hide fields; inspect JSON directly when it already carries typed attributes. Do not run a format conversion just to inflate the workflow.

Is an attribute a safe rename or a manual semantic split?

Apply mapped renames to code or configuration, but review removals such as http.target and unmapped attributes by hand before shipping collector rules.

Is the release failure propagation, trace shape, or latency?

Validate headers for context continuity, inspect the exported waterfall for actual span linkage, and use a latency budget only when a target exists.

Done when

  • A before/after inventory identifies renamed, removed, and still-unmapped attributes in a sanitized fixture and records the target convention version.
  • W3C traceparent, tracestate and baggage plus the relevant OTLP content headers pass validation, and a representative two-hop request keeps one trace-id with distinct span identifiers.
  • A post-change trace export contains the expected service hops, parent-child order, timings, and any error spans; missing spans are listed, not inferred from valid headers alone.
  • If latency is a release criterion, measured spans are compared with a documented stage budget without presenting a single trace as a measured P99.
Hub

Observability Debugging from Logs, Traces, Webhooks, and JSON Payloads

Parse logs, decode traces, inspect webhook/API evidence, explore JSON payloads, and extract recurring patterns before writing an incident-ready debugging note.

Hub

PII Detection and Log Redaction Review

Find likely personal data in logs, text, and PDFs, redact review copies, validate identifier patterns, and require human approval before sharing.

Hub

API Request Format, Replay Preparation, and Debugging Tools

Check request structure, prepare a local replay, compare responses, and debug API clues. These tools analyze or generate locally and do not replace real authentication or server tests.

Home
Tools3212
Workbench
Samples593
Visualizations471
Viewers103
Hubs239
Tags333
Images, Audio & Video657

Image, audio, and video processing, conversion, and optimization tools

Math, Date & Finance647

Calculators, numerics, date logic, statistics, and finance tools

Design & Color298

Color, layout, graphics, visual styling, and design helper tools

Text & Writing209

Writing, cleanup, formatting, extraction, and text analysis tools

Developer & Web193

Developer utilities, networking, web debugging, and automation helpers

Conversion & Encoding175

Format, file, archive, unit, and encoding conversion tools

Lead Generation Quiz Launch and Contact Handoff
Memorial Drafts: Family Review and Print Handoff
Private Habit Records: Backup, Restore and Sharing Review
Article to X and LinkedIn Drafts: Fact Review and Handoff
Markdown Interactive Deck Review and Offline Handoff

© 2026 Elysia Tools. All rights reserved.

DocsPricingAboutTerms of ServicePrivacy PolicyCookiesContact
5

Compare the result with the latency budget

When an SLO target exists, place observed span durations beside the agreed stage allocations and record any over-budget segment for follow-up.

Data Processing

Structured Log Analyzer

Detect common log formats, extract core fields, infer field types, and export parsed logs as JSON, CSV, or SQL inserts

Format Conversion

Logfmt to JSON Structured Log Bridge

Convert logfmt (key=value) to JSON or JSON back to logfmt, with quote escaping, number/boolean coercion, and duplicate-key handling.

Development

OpenTelemetry Semantic-Convention v1.20 → v1.27 Attribute Migration Tool

Rewrites span/log attribute names across OpenTelemetry semantic-convention versions: http.method → http.request.method, http.status_code → http.response.status_code, http.url → url.full, db.system → db.system.name, messaging.destination → messaging.destination.name and 25+ more — applied to pasted JS/TS/Python/Go/Java/.NET source, collector YAML or Grafana dashboard JSON, with an OTel Collector transform rename map, removal/manual-split warnings, per-attribute diff stats and an unmapped-attribute report.

Development

OpenTelemetry W3C traceparent / tracestate / baggage + OTLP Header Propagation Validator

Validate W3C Trace Context propagation headers end to end: traceparent (version / 16-byte trace-id / 8-byte parent-id / trace-flags), tracestate (≤32 list members, tenant keys), baggage (percent-encoded values + opaque properties), OTLP export Content-Type, the gRPC grpc-trace-context-bin 25-byte binary context — plus a two-header correlation round-trip with a random child span-id collision check.

Development

Distributed Trace Decoder & Waterfall Visualizer

Decode Jaeger, Zipkin, or OpenTelemetry trace JSON and render span timing, dependencies, and error hotspots as an interactive waterfall report

Development

API Latency Budget Planner

Plan and visualise an API latency budget. Enter a P99 target (e.g. ≤ 300ms) and per-stage allocations (DNS, TCP, TLS, TTFB, Processing, Network) to see a live waterfall, budget utilisation, and over-budget warnings. Optionally paste an OpenTelemetry or Datadog trace to reverse-engineer a measured allocation.