package jaeger.api_v2

Get desktop application:
View/edit binary Protocol Buffers messages

Note that both Span and Batch may contain a Process. This is different from the Thrift model which was only used for transport, because Proto model is also used by the backend as the domain model, where once a batch is received it is split into individual spans which are all processed independently, and therefore they all need a Process. As far as on-the-wire semantics, both Batch and Spans in the same message may contain their own instances of Process, with span.Process taking priority over batch.Process.

• repeated Span spans = 1

• optional Process process = 2

• string parent = 1

• string child = 2

• uint64 call_count = 3

• string source = 4

Used in: Log, Process, Span

• string key = 1

• ValueType v_type = 2

• string v_str = 3

• bool v_bool = 4

• int64 v_int64 = 5

• double v_float64 = 6

• bytes v_binary = 7

Used in: Span

• optional google.protobuf.Timestamp timestamp = 1

• repeated KeyValue fields = 2

Used in: Batch, Span, Trace.ProcessMapping

• string service_name = 1

• repeated KeyValue tags = 2

Used in: Batch, Trace

• bytes trace_id = 1

• bytes span_id = 2

• string operation_name = 3

• repeated SpanRef references = 4

• uint32 flags = 5

• optional google.protobuf.Timestamp start_time = 6

• optional google.protobuf.Duration duration = 7

• repeated KeyValue tags = 8

• repeated Log logs = 9

• optional Process process = 10

• string process_id = 11

• repeated string warnings = 12

Used in: Span

• bytes trace_id = 1

• bytes span_id = 2

• SpanRefType ref_type = 3

Used in: SpanRef

• CHILD_OF = 0

• FOLLOWS_FROM = 1

• repeated Span spans = 1

• repeated Trace.ProcessMapping process_map = 2

• repeated string warnings = 3

Used in: Trace

• string process_id = 1

• optional Process process = 2

Used in: KeyValue

• STRING = 0

• BOOL = 1

• INT64 = 2

• FLOAT64 = 3

• BINARY = 4