TraceSpan represents an individual span within a distributed trace.
When writing the configuration, the value for the fields associated with this template can either be a
literal or an expression. Please note that if the datatype of a field is not istio.policy.v1beta1.Value,
then the expression’s inferred type must match the datatype of the field.
Trace ID is the unique identifier for a trace. All spans from the same
trace share the same Trace ID.
Span ID is the unique identifier for a span within a trace. It is assigned
when the span is created.
Parent Span ID is the unique identifier for a parent span of this span
instance. If this is a root span, then this field MUST be empty.
Span name is a description of the span’s operation.
For example, the name can be a qualified method name or a file name
and a line number where the operation is called. A best practice is to use
the same display name within an application and at the same call point.
This makes it easier to correlate spans in different traces.
Span tags are a set of < key, value > pairs that provide metadata for the
entire span. The values can be specified in the form of expressions.
HTTP status code used to set the span status. If unset or set to 0, the
span status will be assumed to be successful.
client_span indicates the span kind. True for client spans and False or
not provided for server spans. Using bool instead of enum is a temporary
work around since mixer expression language does not yet support enum
rewriteclientspan_id is used to indicate whether to create a new client
span id to accommodate Zipkin shared span model. Some tracing systems like
Stackdriver separates a RPC into client span and server span. To solve this
incompatibility, deterministically rewriting both span id of client span and
parent span id of server span to the same newly generated id.
Identifies the source (client side) of this span.
Should usually be set to source.workload.name.