Skip to content
semconv.com
↑↓ move↵ openUse with your agent →

Tracked at every release

Every rename, new rule and wire change in OpenTelemetry

Attributes get renamed. Stable documents gain new MUSTs. Fields change on the wire. This site diffs the conventions, the specification and OTLP at every release, so you can check a name, plan an upgrade, or let your agent look it up.

Paste the keys your code emits

One per line, or a whole block of code. Each key is checked against v1.44.0 and the GenAI registry. Nothing leaves your browser.

Your agent gets the same answer from check_attribute_names.

  • renamedhttp.status_code

    use http.response.status_code

  • renameddb.statement

    use db.query.text

  • currentservice.name
  • deprecatednet.peer.name
  • templatehttp.request.header.x-request-id
  • not in registryapp.cart.size

Releases land every few weeks

Every tracked release across the four repositories. Between v1.30.0 and v1.44.0 alone, the conventions made 10 breaking and 418 notable changes.

Compare two versions
Semantic conventions
Specification
OTLP
GenAI conventions
Dec 2024Mar 2025Jun 2025Sep 2025Dec 2025Mar 2026Jun 2026Sep 2026
Height: notable and breaking changesBreakingEach bar opens that release.

All releases and what changed in each

Stop your agent guessing

A model's training data is months behind the registry. Everything here is also a public MCP server with 8 read-only tools. No key, no account. Add it once and your agent can check a name, diff two releases, or quote the spec with a link.

claude mcp add --transport http semconv https://semconv.com/mcp

Tools, example prompts and the JSON API

You

Are the attribute keys in this service still current?

Agent calls

check_attribute_names(names: ["http.status_code", "db.statement", "service.name", "app.cart.size"])

Real tool output, generated from this build's data.

Browse by topic

The registry is one flat list. Each topic gathers its attributes, metrics and spans, plus the spec rules that apply to them.

All 14 topics