Storage schema for trace data

string

Globally unique identifier for the trace. This identifier is a 128-bit numeric value formatted as a 16-byte hexadecimal string. For example, 382d4f4c6b7bb2f4a972559d9085001d. To learn more about this identifier, see W3C trace-id.

A numeric value of zero is invalid.

The trace_id is used by visualization and analysis tools to identify the spans associated with a trace. For this reason, every end-to-end operation must have a unique identifier. Don't reuse a trace identifier.

string

Required. Identifier for the span. Must be unique within a trace. This identifier is a 64-bit numeric value formatted as an 8-byte hexadecimal string. For example, 9046a5b9f7c12500.

A numeric value of zero is invalid.

string

This field corresponds to the tracestate header, as defined by W3C Trace Context. This header contains configuration information that is included in requests when applications are instrumented to collect trace data. For example, an application can specify the probability sampling settings, or it can include vendor-specific content.

OpenTelemetry libraries automatically record the value of the tracestate header when they generate spans.

string

Optional. Identifies the operation which invoked this span. The "root" span has the parent span ID set to null.

The parent-child relationship between spans is used by visualization tools to construct the tree structure.

string

Required. The name of the operation that was performed.

The name can be a method name or some other per-call site name. For the same executable and the same endpoint, using a consistent name makes it easier to correlate cross-trace spans. For best practices, see How to Name Your Spans.

The span name is sanitized and displayed in the Google Cloud console.

integer

Specifies where in the system the operation took place. The value corresponds to the OpenTelemetry: Span Kind enumeration:

Timestamp

Required. Start time of the span, to the nearest nanosecond.

integer

The start time in nanoseconds, according to the UNIX epoch.

Timestamp

Required. End time of the span, to the nearest nanosecond.

integer

The end time in nanoseconds, according to the UNIX epoch.

Timestamp

Required. Receive time of the span, to the nearest nanosecond.

integer

The end time in nanoseconds, according to the UNIX epoch.

integer

The duration in nanoseconds.

JSON type

Each attribute is a key-value pair. The attributes available to you are dependent on your trace data. The structure of attributes follow the OpenTelemetry standard. To learn more, see OpenTelemetry: Attributes.

OpenTelemetry specificies semantic conventions for attributes. To learn about these conventions, see Trace semantic conventions.

The following are examples of attributes:

"yourcompany.your.own.key": "your own value"
"network.protocol.name": "http"
"network.protocol.version": "1.1"
"http.response.status_code": "200"
"network.peer.address": "REDACTED"

integer

The number of attributes that were discarded. Attributes can discarded because their keys are too long or because there are too many attributes. When this value is zero, no attributes were discarded.

This value might be set by the client-side instrumentation or by an application. The value can be incremented by the server.

record with repeated fields

A point in time event. Each event contains the following fields.

integer

The number of events that were discarded. Events can discarded because there are too many events. When this value is zero, no events were discarded.

record with repeated fields

Links associated with the span. Links are references from this span to another span in the same or different trace.

Links provide a mechanism to correlate spans from one trace with spans in another trace. For example, suppose one operation causes an asynchronous operation to occur. In this scenario, there are two traces, one for the original operation and one for the asynchronous operation. You can use links to correlate the spans in these traces.

Each link contains the following fields.

integer

The number of links that were discarded. Links can discarded because there are too many links. When this value is zero, no links were discarded.

record without repeated fields

This field records the completion status for a span. The value of the code subfield corresponds to the OpenTelemetry: Span Status enumeration:

The message subfield, which is formatted a string, contains error information.

record without repeated fields

This field identifies the infrastructure or hosting system from which the telemetry was collected or that the telemetry is about. For example, consider an application running on Google Kubernetes Engine. Attributes for this resource might include the process name and namespace.

This field contains the following subfields:

cloud.account.id: "my-project"
cloud.platform: "gcp_kubernetes_engine"
cloud.provider: "gcp"
cloud.region: "us-central1"
gcp.project_id: "my-project"
host.id: "REDACTED"
host.name: "gke-otel-demo"
k8s.cluster.name: "otel-demo"
k8s.deployment.name: "otel-demo-frontendproxy"

To learn more, see OpenTelemetry: Resources.

record without repeated fields

This field identifies the library or application component for the specified resource that is collecting telemetry. The span represents a specific operation passing through that scope, that is, through the library or component, within the resource.

For example, suppose the application "checkout-service" is deployed to Cloud Run, which means that the resource is a specific Cloud Run instance. Also, assume that the resource has several instrumentation scopes, like "request-authorization-library" and "payment-processor-library".

A client span, like "WritePaymentInfoToStripe", might be a span that is reported by the "payment-processor-library", which is inside the Cloud Run service named "checkout-service".

This field contains the following subfields:

To learn more, see OpenTelemetry: Instrumentation scope.

string

These fields must be a URL formatted as a string.

These fields contain a URL that returns a schema file for a resource. The format of the schema file and data is defined by OpenTelemetry. For more information, see OpenTelemetry: Schemas.

These fields can only be set when using the Telemetry API. That API doesn't validate that the data conforms to the declared schema.

string

These fields must be a URL formatted as a string.

These fields contain a URL that returns a schema file for a scope. The format of the schema file and data is defined by OpenTelemetry. For more information, see OpenTelemetry: Schemas.

These fields can only be set when using the Telemetry API. That API doesn't validate that the data conforms to the declared schema.

record without repeated fields

Application-specific labels are available when trace spans are generated by App Hub applications, when those applications run on supported infrastructure or have been instrumented. To learn more about Application Monitoring and when these labels are available, see Application Monitoring overview.

This field contains application, service, and workload subfields.