View Source OpenTelemetry.Span (opentelemetry_api v1.2.0)

This module contains macros for Span operations that update the active current Span in the current process. An example of creating an Event and adding it to the current Span:

require OpenTelemetry.Tracer, as: Tracer
require OpenTelemetry.Span, as: Span

span_ctx = Tracer.start_span("some-span")
...
Span.add_event(span_ctx, "ecto.query", query: query, total_time: total_time)
...
Span.end_span(span_ctx)

A Span represents a single operation within a trace. Spans can be nested to form a trace tree. Each trace contains a root span, which typically describes the end-to-end latency and, optionally, one or more sub-spans for its sub-operations.

Spans encapsulate:

Link to this section Summary

Functions

Add an event to the currently active Span.

Add a list of events to the currently active Span.

End the Span. Sets the end timestamp for the currently active Span. This has no effect on any child Spans that may exist of this Span.

End the Span. Sets the end timestamp for the currently active Span using the passed in timestamp if valid, current timestamp otherwise. This has no effect on any child Spans that may exist of this Span.

Get the lowercase hex encoded span ID.

Get the lowercase hex encoded trace ID.

Record an exception as an event, following the semantics convetions for exceptions.

Set an attribute with key and value on the currently active Span.

Add a list of attributes to the currently active Span.

Sets the Status of the currently active Span.

Get the SpanId of a Span.

Get the TraceId of a Span.

Get the Tracestate of a Span.

Updates the Span name.

Link to this section Types

@type start_opts() :: :otel_span.start_opts()

Link to this section Functions

Link to this function

add_event(span_ctx, event, attributes)

View Source

Add an event to the currently active Span.

Link to this function

add_events(span_ctx, events)

View Source
@spec add_events(OpenTelemetry.span_ctx(), [OpenTelemetry.event()]) :: boolean()

Add a list of events to the currently active Span.

End the Span. Sets the end timestamp for the currently active Span. This has no effect on any child Spans that may exist of this Span.

The Span Context is returned with is_recording set to false.

Link to this function

end_span(span_ctx, timestamp)

View Source

End the Span. Sets the end timestamp for the currently active Span using the passed in timestamp if valid, current timestamp otherwise. This has no effect on any child Spans that may exist of this Span.

The Span Context is returned with is_recording set to false.

@spec hex_span_id(OpenTelemetry.span_ctx()) :: binary()

Get the lowercase hex encoded span ID.

@spec hex_trace_id(OpenTelemetry.span_ctx()) :: binary()

Get the lowercase hex encoded trace ID.

Link to this function

record_exception(span_ctx, exception, trace \\ nil, attributes \\ [])

View Source

Record an exception as an event, following the semantics convetions for exceptions.

If trace is not provided, the stacktrace is retrieved from Process.info/2

Link to this function

set_attribute(span_ctx, key, value)

View Source

Set an attribute with key and value on the currently active Span.

Link to this function

set_attributes(span_ctx, attributes)

View Source

Add a list of attributes to the currently active Span.

Link to this function

set_status(span_ctx, status)

View Source

Sets the Status of the currently active Span.

If used, this will override the default Span Status, which is :unset.

Get the SpanId of a Span.

Get the TraceId of a Span.

Get the Tracestate of a Span.

Link to this function

update_name(span_ctx, name)

View Source

Updates the Span name.

It is highly discouraged to update the name of a Span after its creation. Span name is often used to group, filter and identify the logical groups of spans. And often, filtering logic will be implemented before the Span creation for performance reasons. Thus the name update may interfere with this logic.

The function name is called UpdateName to differentiate this function from the regular property setter. It emphasizes that this operation signifies a major change for a Span and may lead to re-calculation of sampling or filtering decisions made previously depending on the implementation.