package opentelemetry.proto.trace.v1

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message ResourceSpans

trace.proto:48

A collection of ScopeSpans from a Resource.

Used in: collector.trace.v1.ExportTraceServiceRequest, TracesData

message ScopeSpans

trace.proto:64

A collection of Spans produced by an InstrumentationScope.

Used in: ResourceSpans

message Span

trace.proto:80

A Span represents a single operation performed by a single component of the system. The next available field id is 17.

Used in: ScopeSpans

message Span.Event

trace.proto:193

Event is a time-stamped annotation of the span, consisting of user-supplied text description and key-value pairs.

Used in: Span

trace.proto:222

A pointer from the current span to another span in the same trace or in a different trace. For example, this can be used in batching operations, where a single batch handler processes multiple requests from different traces or when the handler receives a request from a different project.

Used in: Span

enum Span.SpanKind

trace.proto:121

SpanKind is the type of span. Can be used to specify additional relationships between spans in addition to a parent/child relationship.

Used in: Span

message Status

trace.proto:258

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs.

Used in: Span

enum Status.StatusCode

trace.proto:266

For the semantics of status codes see https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#set-status

Used in: Status

message TracesData

trace.proto:38

TracesData represents the traces data that can be stored in a persistent storage, OR can be embedded by other protocols that transfer OTLP traces data but do not implement the OTLP protocol. The main difference between this message and collector protocol is that in this message there will not be any "control" or "metadata" specific to OTLP protocol. When new fields are added into this message, the OTLP request MUST be updated as well.