This is documentation for the next version of Tempo. For the latest stable release, go to the latest version.
Apache Parquet schema
Starting with Tempo 2.0, Apache Parquet is used as the default column-formatted block format. Refer to the Parquet configuration options for more information.
This document describes the schema used with the Parquet block format.
Fully nested versus span-oriented schema
There are two overall approaches to a columnar schema: fully nested or span-oriented. Span-oriented means a flattened schema where traces are destructured into rows of spans. A fully nested schema means the current trace structures such as Resource/Scope/Spans/Events are preserved (nested data is natively supported in Parquet). In both cases, individual leaf values such as span name and duration are individual columns.
We chose the nested schema for several reasons:
- The block size is much smaller for the nested schema. This is due to the high data duplication incurred when flattening resource-level attributes such as
service.name
to each individual span. - A flat schema is not truly “flat” because each span still contains nested data such as attributes and events.
- Nested schema is much faster to search for resource-level attributes because the resource-level columns are very small (1 row for each batch).
- Translation to and from the OpenTelemetry Protocol Specification (OTLP) is straightforward.
- Easily add computed columns (for example, trace duration) at multiple levels such as per-trace, per-batch, etc.
Static vs dynamic columns
Dynamic vs static columns add another layer to the schema.
A dynamic schema stores each attribute such as service.name
and http.status_code
as its own column and the columns in each parquet file can be different.
A static schema is unresponsive to the shape of the data, and all attributes are stored in generic key/value containers.
The dynamic schema is the ultimate dream for a columnar format but it is too complex for a first release. However, the benefits of that approach are also too good to pass up, so we propose a hybrid approach. It is primarily a static schema but with some dynamic columns extracted from trace data based on some heuristics of frequently queried attributes. We plan to continue investing in this direction to implement a fully dynamic schema where trace attributes are blown out into independent Parquet columns at runtime.
For more information, refer to the Parquet design document.
Schema details
The adopted Parquet schema is mostly a direct translation of OTLP but with some key differences.
The table below uses these abbreviations:
rs
- resource spansss
- scope spans
Name | Type | Description |
TraceID | byte array | The trace ID in 16-byte binary form. |
TraceIDText | string | The trace ID in hexadecimal text form. |
StartTimeUnixNano | int64 | Start time of the first span in the trace, in nanoseconds since unix epoch. |
EndTimeUnixNano | int64 | End time of the last span in the trace, in nanoseconds since unix epoch. |
DurationNano | int64 | Total trace duration in nanoseconds, computed as difference between EndTimeUnixNano and StartTimeUnixNano. |
RootServiceName | string | The resource-level service.name attribute (rs.Resource.ServiceName) from the root span of the trace if one exists, else null. |
RootSpanName | string | The name (rs.ss.Spans.Name) of the root span if one exists, else null. |
rs | Short-hand for ResourceSpans | |
rs.Resource.ServiceName | string | A dedicated column for the resource-level service.name attribute if present. https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/#service |
rs.Resource.Cluster | string | A dedicated column for the resource-level cluster attribute if present and of string type. Values of other types will be stored in the generic attribute columns. |
rs.Resource.Namespace | string | A dedicated column for the resource-level namespace attribute if present and of string type. Values of other types will be stored in the generic attribute columns. |
rs.Resource.Pod | string | A dedicated column for the resource-level pod attribute if present and of string type. Values of other types will be stored in the generic attribute columns. |
rs.Resource.Container | string | A dedicated column for the resource-level container attribute if present and of string type. Values of other types will be stored in the generic attribute columns. |
rs.Resource.K8sClusterName | A dedicated column for the resource-level k8s.cluster.name attribute if present and of string type. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/k8s/#cluster | |
rs.Resource.K8sNamespaceName | string | A dedicated column for the resource-level k8s.namespace.name attribute if present and of string type. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/k8s/#namespace |
rs.Resource.K8sPodName | string | A dedicated column for the resource-level k8s.pod.name attribute if present and of string type. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/k8s/#pod |
rs.Resource.K8sContainerName | string | A dedicated column for the resource-level k8s.container.name attribute if present and of string type. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/resource/semantic_conventions/k8s/#container |
rs.Resource.Attrs.Key | string | All resource attributes that do not have a dedicated column are stored as a key value pair in these columns. The Key column stores the name, and then one of the Value columns is populated according to the attribute’s data type. The other value columns will contain null. |
rs.Resource.Attrs.Value | string | The attribute value if string type, else null. |
rs.Resource.Attrs.ValueInt | int | The attribute value if integer type, else null. |
rs.Resource.Attrs.ValueDouble | float | The attribute value if float type, else null. |
rs.Resource.Attrs.ValueBool | bool | The attribute value if boolean type, else null. |
rs.Resource.Attrs.ValueArray | byte array | The attribute value if nested array type, else null. Protocol buffer encoded binary data. |
rs.Resource.Attrs.ValueKVList | byte array | The attribute value if nested key/value map type, else null. Protocol buffer encoded binary data. |
rs.Resource.DedicatedAttributes | Group containing spares for dedicated attribute columns with resource scope | |
rs.Resource.DedicatedAttributes.String01 … String10 | string | 10 spare columns for dedicated attribute columns |
rs.ss | Shorthand for ResourceSpans.ScopeSpans | |
rs.ss.Scope | Shorthand for ResourceSpans.ScopeSpans.Scope | |
rs.ss.Scope.Name | string | Scope name if present, else empty string. https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-scope |
rs.ss.Scope.Version | string | The Scope version if present, else empty string. https://opentelemetry.io/docs/specs/otel/glossary/#instrumentation-scope |
rs.ss.Spans.SpanID | byte array | Span unique ID. |
rs.ss.Spans.ParentSpanID | byte array | The unique ID of the span’s parent. For root spans without a parent this is null. |
rs.ss.Spans.ParentID | int32 | Trace local numeric parent ID. |
rs.ss.Spans.NestedSetLeft | int32 | Left bound of the nested set model. Also used as a trace local numeric span ID. |
rs.ss.Spans.NestedSetRight | int32 | Right bound of the nested set model. |
rs.ss.Spans.Name | string | Span name. |
rs.ss.Spans.StartTimeUnixNano | int64 | Start time the span in nanoseconds since unix epoch. |
rs.ss.Spans.DurationNano | int64 | Span duration in nanoseconds. |
rs.ss.Spans.Kind | int | The span’s kind. Defined values: 0. Unset; 1. Internal; 2. Server; 3. Client; 4. Producer; 5. Consumer; https://opentelemetry.io/docs/reference/specification/trace/api/#spankind |
rs.ss.Spans.StatusCode | int | The span status. Defined values: 0: Unset; 1: OK; 2: Error. https://opentelemetry.io/docs/reference/specification/trace/api/#set-status |
rs.ss.Spans.StatusMessage | string | Optional message to accompany Error status. |
rs.ss.Spans.HttpMethod | string | A dedicated column for the span-level http.method attribute if present and of string type, else null. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/http/#common-attributes |
rs.ss.Spans.HttpStatusCode | int | A dedicated column for the span-level http.status_code attribute if present and of integer type, else null. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/http/#common-attributes |
rs.ss.Spans.HttpUrl | string | A dedicated column for the span-level http.url attribute if present and of string type, else null. Values of other types will be stored in the generic attribute columns. https://opentelemetry.io/docs/reference/specification/trace/semantic_conventions/http/#http-client |
rs.ss.Spans.DroppedAttributesCount | int | Number of attributes that were dropped |
rs.ss.Spans.Attrs.Key | string | All span attributes that do not have a dedicated column are stored as a key value pair in these columns. The Key column stores the name, and then one of the Value columns is populated according to the attribute’s data type. The other value columns will contain null. |
rs.ss.Spans.Attrs.Value | string | The attribute value if string type, else null. |
rs.ss.Spans.Attrs.ValueInt | int | The attribute value if integer type, else null. |
rs.ss.Spans.Attrs.ValueDouble | float | The attribute value if float type, else null. |
rs.ss.Spans.Attrs.ValueBool | bool | The attribute value if boolean type, else null. |
rs.ss.Spans.Attrs.ValueArray | byte array | The attribute value if nested array type, else null. Protocol buffer encoded binary data. |
rs.ss.Spans.Attrs.ValueKVList | byte array | The attribute value if nested key/value map type, else null. Protocol buffer encoded binary data. |
rs.ss.Spans.DedicatedAttributes | Group containing spares for dedicated attribute columns with span scope | |
rs.ss.Spans.DedicatedAttributes.String01 … String10 | string | 10 spare columns used for dedicated attributes |
rs.ss.Spans.DroppedEventsCount | int | The number of events that were dropped |
rs.ss.Spans.Events.TimeUnixNano | int64 | The timestamp of the event, as nanoseconds since unix epoch. |
rs.ss.Spans.Events.Name | string | The event name or message. |
rs.ss.Spans.Events.DroppedAttributesCount | int | The number of event attributes that were dropped. |
rs.ss.Spans.Events.Attrs.Key | string | All event attributes are stored as a key value pair in these columns. The Key column stores the name. |
rs.ss.Spans.Events.Attrs.Value | byte array | The attribute value, Protocol buffer encoded binary data. |
rs.ss.Spans.DroppedLinksCount | int | The number of links that were dropped. |
rs.ss.Spans.Links | byte array | Protocol-buffer encoded span links if present, else null. |
rs.ss.Spans.TraceState | string | The span’s TraceState value if present, else empty string.https://opentelemetry.io/docs/reference/specification/trace/api/#tracestate |
To increase the readability table omits the groups list.element
that are added for nested list types in Parquet.
Block Schema display in Parquet Message format
message Trace {
required binary TraceID;
required binary TraceIDText (STRING);
required int64 StartTimeUnixNano (INTEGER(64,false));
required int64 EndTimeUnixNano (INTEGER(64,false));
required int64 DurationNano (INTEGER(64,false));
required binary RootServiceName (STRING);
required binary RootSpanName (STRING);
required group rs (LIST) {
repeated group list {
required group element {
required group Resource {
required group Attrs (LIST) {
repeated group list {
required group element {
required binary Key (STRING);
optional binary Value (STRING);
optional int64 ValueInt (INTEGER(64,true));
optional double ValueDouble;
optional boolean ValueBool;
optional binary ValueKVList (STRING);
optional binary ValueArray (STRING);
}
}
}
required binary ServiceName (STRING);
optional binary Cluster (STRING);
optional binary Namespace (STRING);
optional binary Pod (STRING);
optional binary Container (STRING);
optional binary K8sClusterName (STRING);
optional binary K8sNamespaceName (STRING);
optional binary K8sPodName (STRING);
optional binary K8sContainerName (STRING);
required group DedicatedAttributes {
optional binary String01 (STRING);
optional binary String02 (STRING);
optional binary String03 (STRING);
optional binary String04 (STRING);
optional binary String05 (STRING);
optional binary String06 (STRING);
optional binary String07 (STRING);
optional binary String08 (STRING);
optional binary String09 (STRING);
optional binary String10 (STRING);
}
}
required group ss (LIST) {
repeated group list {
required group element {
required group Scope {
required binary Name (STRING);
required binary Version (STRING);
}
required group Spans (LIST) {
repeated group list {
required group element {
required binary SpanID;
required binary ParentSpanID;
required int32 ParentID (INTEGER(32,true));
required int32 NestedSetLeft (INTEGER(32,true));
required int32 NestedSetRight (INTEGER(32,true));
required binary Name (STRING);
required int64 Kind (INTEGER(64,true));
required binary TraceState (STRING);
required int64 StartTimeUnixNano (INTEGER(64,false));
required int64 DurationNano (INTEGER(64,false));
required int64 StatusCode (INTEGER(64,true));
required binary StatusMessage (STRING);
required group Attrs (LIST) {
repeated group list {
required group element {
required binary Key (STRING);
optional binary Value (STRING);
optional int64 ValueInt (INTEGER(64,true));
optional double ValueDouble;
optional boolean ValueBool;
optional binary ValueKVList (STRING);
optional binary ValueArray (STRING);
}
}
}
required int32 DroppedAttributesCount (INTEGER(32,true));
required group Events (LIST) {
repeated group list {
required group element {
required int64 TimeUnixNano (INTEGER(64,false));
required binary Name (STRING);
required group Attrs (LIST) {
repeated group list {
required group element {
required binary Key (STRING);
required binary Value;
}
}
}
required int32 DroppedAttributesCount (INTEGER(32,true));
}
}
}
required int32 DroppedEventsCount (INTEGER(32,true));
required binary Links;
required int32 DroppedLinksCount (INTEGER(32,true));
optional binary HttpMethod (STRING);
optional binary HttpUrl (STRING);
optional int64 HttpStatusCode (INTEGER(64,true));
required group DedicatedAttributes {
optional binary String01 (STRING);
optional binary String02 (STRING);
optional binary String03 (STRING);
optional binary String04 (STRING);
optional binary String05 (STRING);
optional binary String06 (STRING);
optional binary String07 (STRING);
optional binary String08 (STRING);
optional binary String09 (STRING);
optional binary String10 (STRING);
}
}
}
}
}
}
}
}
}
}
}
Trace-level attributes
For speed and ease-of-use, we are projecting several values to columns at the trace-level:
- Trace ID - Don’t store on each span.
- Root service/span names/StartTimeUnixNano - These are selected properties of the root span in each trace (if there is one). These are used for displaying results in the Grafana UI. These properties are computed at ingest time and stored once for efficiency, so we don’t have to find the root span.
DurationNanos
- The total trace duration, computed at ingest time. This powers the min/max duration filtering in the current Tempo search and is more efficient than scanning the spans duration column. However, it may go away with TraceQL or we could decide to change it to span-level duration filtering too.
Well-known attributes
Projecting attributes to their own columns has benefits for search speed and size. Therefore, we are taking an opinionated approach and store some well-known attributes to their own dedicated columns. All other attributes are stored in the generic key/value maps and are still searchable, but not as quickly. We chose these attributes based on the OTEL semantic-conventions and what we commonly use ourselves (scratching our own itch), but we think they will be useful to most workloads.
Resource-level attributes include the following:
service.name
cluster
andk8s.cluster.name
namespace
andk8s.namespace.name
pod
andk8s.pod.name
container
andk8s.container.name
Span-level attributes include the following:
http.method
http.url
http.status_code
(int)
“Any”-type Attributes
OTLP attributes have variable data types, which is easy to accomplish in formats like protocol-buffers, but does not translate directly to Parquet.
Each column must have a concrete type.
There are several possibilities here but we chose to have optional values for each concrete type.
Array
and KeyValueList
types are stored as protocol-buffer-encoded byte arrays.
repeated group Attrs {
required binary Key (STRING);
# Only one of these will be set
optional binary Value (STRING);
optional boolean ValueBool;
optional double ValueDouble;
optional int64 ValueInt (INT(64,true));
optional binary ValueArray (STRING);
optional binary ValueKVList (STRING);
}
Event attributes
Event attributes are stored as protocol-buffer encoded.
repeated group Attrs {
required binary Key (STRING);
required binary Value (STRING);
}
Compression and encoding
Parquet has robust support for many compression algorithms and data encodings. We have found excellent combinations of storage size and performance with the following:
- Snappy Compression - Enable on all columns
- Dictionary encoding - Enable on all string columns (including byte array ParentSpanID). Most strings are very repetitive so this works well to optimize storage size. However we can greatly speed up search by inspecting the dictionary first and eliminating pages with no matches.
- Time and duration unix nanos - Delta encoding
- Rarely used columns such as
DroppedAttributesCount
- These columns are usually all zeroes, RLE works well.
Bloom filters
Parquet has native support for bloom filters. However, Tempo does not use them at this time. Tempo already has sophisticated support for sharding and caching bloom filters.