package opentelemetry

  1. Overview
  2. Docs
Core library for instrumentation and serialization for https://opentelemetry.io

Install

dune-project
 Dependency

Authors

Maintainers

Sources

opentelemetry-0.90.tbz
sha256=c3989bb678f57e5276209d3c60afb29cdca33122288de55e591fbbe2e50a662c
sha512=ba8339256c9b2d8c99c8304991a3047f280a01e492add4cf82bf1d43dfa51e790366c09c6901c0501b8b8e1f810c6e128e33dd33542d785013407f642ade4eea

doc/opentelemetry.core/Opentelemetry_core/Span_ctx/index.html

Module Opentelemetry_core.Span_ctxSource

Span context. This bundles up a trace ID and parent ID.

https://opentelemetry.io/docs/specs/otel/trace/api/#spancontext

  • since 0.7
Sourcetype t
Sourceval make : ?remote:bool -> ?sampled:bool -> trace_id:Trace_id.t -> parent_id:Span_id.t -> unit -> t
Sourceval dummy : t

Invalid span context, to be used as a placeholder

Sourceval is_remote : t -> bool

Does this come from a remote parent?

Sourceval is_valid : t -> bool

Are the span ID and trace ID valid (ie non-zero)?

Sourceval trace_id : t -> Trace_id.t
Sourceval parent_id : t -> Span_id.t
Sourceval sampled : t -> bool
Sourceval to_w3c_trace_context : t -> bytes
Sourceval of_w3c_trace_context : bytes -> (t, string) result
Sourceval of_w3c_trace_context_exn : bytes -> t
Sourceval k_ambient : t Hmap.key

Hmap key to carry around a Span_ctx.t, e.g. to remember what the current parent span is.

  • since 0.8