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.
Mobile
| Attribute | Type | Description | Examples |
|---|---|---|---|
blocked_main_thread | boolean | Whether the main thread was blocked by the span. | true |
call_stack | StackFrame[] | The most relevant stack frames, that lead to the File I/O span. The stack frame should adhere to the StackFrame interface. |
Browser
| Attribute | Type | Description | Examples |
|---|---|---|---|
url | string | The URL of the resource that was fetched. | https://example.com |
method | string | The HTTP method used. | GET |
type | string | The type of the resource that was fetched. | xhr |
Encoded Body Size | string | The encoded body size of the request. | 123 B |
Decoded Body Size | string | The decoded body size of the request. | 456 B |
Transfer Size | string | The transfer size of the request. | 789 B |
You can edit this page on GitHub.