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
- 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.
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/mcpcodex mcp add semconv --url https://semconv.com/mcp.cursor/mcp.json
{
"mcpServers": {
"semconv": { "url": "https://semconv.com/mcp" }
}
}.vscode/mcp.json
{
"servers": {
"semconv": { "type": "http", "url": "https://semconv.com/mcp" }
}
}Streamable HTTP, no auth, no session
{
"mcpServers": {
"semconv": { "type": "streamable-http", "url": "https://semconv.com/mcp" }
}
}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"])
- renamedhttp.status_codeuse http.response.status_code
- renameddb.statementuse db.query.text
- currentservice.name
- not in registryapp.cart.size
You
We built against v1.30.0. Which database attributes were renamed since?
Agent calls
diff_versions(source: "semconv", from: "1.30.0", to: "1.44.0")
- renameddb.systemdb.system.name
- renameddb.namedb.namespace
- renameddb.operationdb.operation.name
- renameddb.statementdb.query.text
- and 21 more
You
What does the spec require when an export fails with a transient error?
Agent calls
search_requirements(query: "retry", section: "protocol")
Transient errors MUST be handled with a retry strategy.
This retry strategy MUST implement an exponential back-off with jitter to avoid overwhelming the destination until the network is restored or the destination has recovered.
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.