Attribute Registry

The attributes registry is the place where attributes are defined. An attribute definition covers the following properties of an attribute:

• the id (the fully qualified name) of the attribute
• the type of the attribute
• the stability of the attribute
• a brief description of the attribute and optionally a longer note
• example values

Attributes defined in the registry can be used in different semantic conventions. Attributes should be included in this registry before they are used in semantic conventions. Semantic conventions may override all the properties of an attribute except for the id and type in case it’s required for a particular context. In addition, semantic conventions specify the requirement level of an attribute in the corresponding context.

A definition of an attribute in the registry doesn’t necessarily imply that the attribute is used in any of the semantic conventions.

If applicable, application developers are encouraged to use existing attributes from this registry. See also these recommendations regarding attribute selection and attribute naming for custom use cases.

All registered attributes are listed by namespace in this registry.

Warning The following registry overview is a work in progress.

Further attribute namespaces are currently being migrated and will appear in this registry soon.

Currently, the following namespaces exist:

• Android
• Artifact
• Aspnetcore
• AWS
• Azure
• Browser
• CICD
• Client
• Cloud
• CloudEvents
• CloudFoundry
• Code
• Container
• CPU
• Db
• Deployment
• Destination
• Device
• Disk
• Dns
• Dotnet
• Enduser
• Error
• Event
• Exception
• Faas
• Feature Flag
• File
• GCP
• Gen AI
• Go
• GraphQL
• Hardware
• Heroku
• Host
• HTTP
• iOS
• JVM
• K8s
• Linux
• Log
• Messaging
• Network
• NodeJS
• OCI
• OpenTracing
• OS
• OTel
• Peer
• Process
• Profile
• RPC
• Server
• Service
• Session
• SignalR
• Source
• System
• Telemetry
• Test
• Thread
• TLS
• URL
• User
• User Agent
• V8js
• VCS
• Webengine