Span Data Conventions

The Span Interface specifies a series of timed application events that have a start and end time. Below describes the conventions for the Span interface for the data field on the span.

The data field on the span is expected to follow OpenTelemetry's semantic conventions for attributes as much as possible.

Keys on the data field should be lower-case and use underscores instead of camel-case. There are some exceptions to this, but these exist because of backwards compatability.

Below describes the conventions for the Span interface for the data field on the span that are currently used by the product or are important to bring up.

HTTP

AttributeTypeDescriptionExamples
http.querystringThe Query string present in the URL.?foo=bar&bar=baz
http.fragmentstringThe Fragments present in the URI (Browser SDKs only).#foo=bar
http.request.methodstringThe HTTP method used.GET
http.response.status_codeintThe status HTTP response.404
http.response_content_lengthnumberThe encoded body size of the response (in bytes).123
http.decoded_response_body_lengthnumberThe decoded body size of the response (in bytes).456
http.response_transfer_sizenumberThe transfer size of the response (in bytes).789

Mobile

AttributeTypeDescriptionExamples
blocked_main_threadbooleanWhether the main thread was blocked by the span.true
call_stackStackFrame[]The most relevant stack frames, that lead to the File I/O span. The stack frame should adhere to the StackFrame interface.
urlstringThe URL of the resource that was fetched.https://example.com
typestringMore granular type of the operation happening.fetch

Browser

AttributeTypeDescriptionExamples
urlstringThe URL of the resource that was fetched.https://example.com
typestringThe type of the resource that was fetched.xhr
resource.render_blocking_statusstringThe render blocking status of the resource.non-blocking

Database

AttributeTypeDescriptionExamples
db.systemstringAn identifier for the database management system (DBMS) product being used. See OpenTelemetry docs for a list of well-known identifiers.postgresql
db.operationstringThe name of the operation being executed, e.g. the MongoDB command name such as findAndModify, or the SQL keyword. Based on OpenTelemetry's call level db attributesSELECT
db.namestringThis attribute is used to report the name of the database being accessed. For commands that switch the database, this should be set to the target database (even if the command fails).customers
server.addressstringName of the database host.example.com
server.portintLogical server port number host.8080
server.socket.addressstringPhysical server IP address or Unix socket address. host.10.5.3.2
server.socket.portintPhysical server port. host.16456

Web Server

AttributeTypeDescriptionExamples
cache.hitbooleanIf the cache was hit during this span.true
cache.item_sizeintThe size of the requested item in the cache. In bytes.58

Thread

AttributeTypeDescriptionExamples
thread.idstringThread identifier of the thread that the span originated from.123456
thread.namestringThread label identifying a thread.main

Deprecated

Names that SDKs are still sending so we cannot remove them yet, but should not be used in new code.

AttributeNew name
methodhttp.request.method
http.methodhttp.request.method
Encoded Body Sizehttp.response_content_length
Decoded Body Sizehttp.decoded_response_body_length
Transfer Sizehttp.response_transfer_size
You can edit this page on GitHub.