Legend:
Page
Library
Module
Module type
Parameter
Class
Class type
Source
Page
Library
Module
Module type
Parameter
Class
Class type
Source
explicit_span_ctx
as parent, that can potentially be transmitted across processes/machines. It also is intended to be more compatible with OTEL.trace.subscriber
: timestamps are int64
ns now, not floatstrace
: pass a string
trace_id in manual spans, which helps for backends such as opentelemetry. It's also useful for extensions.trace-fuchsia
: full revamp of the library, modularized, using subscriber APItrace-tef
: split into exporter,writer,subscriber, using subscriber APItrace.event
, useful for background threadstrace.subscriber
: add Span_tbl
, and a depopt on picos_auxtrace.subscriber
: tee a whole array at oncetrace.subscriber
: depopt on unix for timestampstrace-tef
: depopt on unix for TEF timestampstrace.subscriber
instead of a separate librarytrace-tef.tldrs
, to trace multiple processes easily (with external rust daemon)trace-tef
: use mtime.now
, not a counter, for multiproctrace-fuchsia
: require thread-local-storage 0.2Trace_core
. Levels are similar to logs
levels, to help control verbosity.add ppx_trace
for easier instrumentation.
let%trace span = "foo" in …
will enter a scope span
named "foo"let%trace () = "foo" in …
will enter a scope named "foo" with a hidden nametrace-fuchsia
backend, which produces traces in the binary format of fuchsia. These traces are reasonably efficient to produce (~60ns per span on my machines) and reasonably compact on disk, at least compared to the TEF backend.?data
to counter_int
and counter_float
float
to user dataadd_data_to_current_span
and add_data_to_manual_span
explicit_span.meta
mutabletrace.json
if env variable TRACE
is either 1 or truewith_setup
; env for "stdout"/"stderr"Trace
module by adding sublibrary trace.core
. Programs that use compiler-libs.toplevel
should use trace.core
directly, because using trace
will cause linking errors.initial release