Crate sp_tracing
source ·Expand description
Substrate tracing primitives and macros.
To trace functions or invidual code in Substrate, this crate provides within_span
and enter_span
. See the individual docs for how to use these macros.
Note that to allow traces from wasm execution environment there are
2 reserved identifiers for tracing Field
recording, stored in the consts:
WASM_TARGET_KEY
and WASM_NAME_KEY
- if you choose to record fields, you
must ensure that your identifiers do not clash with either of these.
Additionally, we have a const: WASM_TRACE_IDENTIFIER
, which holds a span name used
to signal that the ‘actual’ span name and target should be retrieved instead from
the associated Fields mentioned above.
Note: The tracing
crate requires trace metadata to be static. This does not work
for wasm code in substrate, as it is regularly updated with new code from on-chain
events. The workaround for this is for the wasm tracing wrappers to put the
name
and target
data in the values
map (normally they would be in the static
metadata assembled at compile time).
Modules
Macros
Event
.Structs
event!
or span!
.
Generally generated automaticaly via stringify
from an 'static &str
.
Likely print-able.WasmFieldName
s in the order providedspan!
or event!
call on the wasm-side.WasmFieldName
s with the given WasmValue
(if provided)
in the order specified.Enums
Statics
tracing
system