OpenTelemetry attributes: semantic conventions lookup

Type part of an attribute name, such as gen_ai.agent or status_code. Each result shows its type and stability, and links to the spans that set it, real values and renamed names.

From semantic-conventions v1.44.0, semantic-conventions-genai at 547934a and hashspan core 1.3.1Synced View as MarkdownOpen in ClaudeOpen in ChatGPT

Which attribute namespaces does it cover?

The OpenTelemetry namespaces an agent or a service that talks to a blockchain node uses most, and hashspan's own. Each has a page with the spans that set it and the names it replaced.

NamespacePageNames
gen_ai.*gen_ai.* attributes79
mcp.*gen_ai.* attributes4
rpc.*rpc.* and jsonrpc.* attributes6
jsonrpc.*rpc.* and jsonrpc.* attributes2
http.*http.* attributes12
error.*error.type1
server.*server.address and server.port2
client.*server.address and server.port2
blockchain.*hashspan semantic conventions53
x402.*hashspan semantic conventions2
mpp.*hashspan semantic conventions5

What do the stability levels mean?

  • Stable. The name and its meaning stay. http.request.method, error.type and server.address are Stable.
  • Release candidate. Ready to become Stable; breaking changes only in special cases. The core rpc.* attributes are here in v1.44.0.
  • Development. Can still be renamed or removed. Every gen_ai.* and mcp.* attribute is Development, and so is every hashspan attribute.
  • Deprecated. Replaced or removed. Hidden by default above; each one says what replaced it.

Where do these names come from?

From the model files that the official registry is built from: open-telemetry/semantic-conventions at v1.44.0, and open-telemetry/semantic-conventions-genai at commit 547934a, because the GenAI conventions moved there in 2026 and have no release yet. A script reads them at a pinned version and keeps names, types, stability, one-line descriptions and the spans that reference each name. Every row links to the official definition.

hashspan's own blockchain.*, x402.* and mpp.* rows come from its semantic conventions at @hashspan/core@1.3.1, the version on npm. OpenTelemetry has no blockchain conventions yet, so these are hashspan's namespace, not OpenTelemetry's.

FAQ

Is this the official OpenTelemetry attribute registry?

No. It is generated from the official model files at a pinned version, and every attribute links to its entry in the official registry. Where the two disagree, the official registry wins.

Why are the gen_ai.* attributes not shown as deprecated here?

The main semantic-conventions repository marks them deprecated because they moved to the semantic-conventions-genai repository. This list takes them from the new repository, where they are current. Only names that were really renamed or removed are marked Deprecated.

What do Release candidate and Development mean?

Development names can still be renamed or removed. A Release candidate is ready to become Stable, and breaking changes are allowed only in special cases. Stable names keep their meaning.

OpenTelemetry attribute names, types, stability and descriptions: © OpenTelemetry Authors, Apache-2.0, from open-telemetry/semantic-conventions (semantic-conventions v1.44.0 (e10a930)) and open-telemetry/semantic-conventions-genai.

Something wrong or out of date? Report a problem with this page.

Type to search the docs, Learn topics and the blog.