Which semantic convention namespaces are migrated between v1.20 and v1.27?

The tool migrates HTTP attributes (v1.23.1 stable), database attributes like db.system to db.system.name (v1.24.0), and messaging namespaces like messaging.destination (v1.27.0).

Why are attributes like http.target flagged instead of automatically renamed?

Attributes like http.target were removed rather than renamed because they require manual splitting into separate url.path and url.query fields.

Can this tool update raw Grafana dashboard JSON files?

Yes, enabling the dashboard option performs whole-token attribute renames inside JSON query strings and panel definitions.

How does the OpenTelemetry Collector rename map output work?

It generates an attributes processor or transform processor YAML block with action rename rules to bridge telemetry versions at the collector level.

Does the tool support partial keyword matching?

No, it utilizes whole-token matching to prevent accidental renames of unrelated variable names or substrings.

Elysia Tools

Navigation

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.

Details

What this tool helps you do

Paste code (any language), an OTel Collector config, or a Grafana dashboard JSON; choose the source and target convention versions. The engine applies the official non-normative migration tables layer by layer — v1.23.1 stabilizes the HTTP conventions, v1.24 renames the database attributes, v1.27 rewrites messaging. Whole-token matching prevents partial matches. Removed attributes (http.target, net.sock.family, net.sock.peer.name) are flagged instead of rewritten — http.target must be split manually into url.path and url.query. Output: rewritten source with a diff summary, the collector transform rename map, dashboard JSON synchronization, and any old-style attribute left unmapped for manual review.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Samples

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

What this tool helps you do

Run this tool

Examples that match this tool

Continue with connected tools and hubs

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Migrating Node.js HTTP and Database Telemetry

2. Updating Python WSGI Middleware to v1.23.1 HTTP Semantics

FAQ

Distributed Tracing Samples

Parcel Bundler Samples

OpenAPI/Swagger Samples

pnpm Package Manager Samples

JSON Schema to Zod Schema Converter

OpenAPI to Postman Collection

OpenAPI to TypeScript Generator

Bulk Email Extractor

Verify an OpenTelemetry Instrumentation Upgrade