Substrate's client telemetry is a part of substrate that allows logging telemetry information with a Polkadot telemetry.
It works using Tokio's tracing. The telemetry
information uses tracing's logging to report the telemetry which is then retrieved by a
Layer. This layer will then send the data through an asynchronous channel and to a
background task called
TelemetryWorker which will send the information to the telemetry
If multiple substrate nodes are running, it uses a tracing's
Span to identify which substrate
node is reporting the telemetry. Every task spawned using sc-service's
automatically inherit this span.
Substrate's nodes initialize/register to the
TelemetryWorker using a
This handle can be cloned and passed around. It uses an asynchronous channel to communicate with
TelemetryWorker dedicated to registration. Registering a telemetry can happen at
any point in time during the execution.
Report a telemetry.
Message sent when the connection (re-)establishes.
Used to create a stream of events with only one event: when a telemetry connection (re-)establishes.
List of telemetry servers we want to talk to. Contains the URL of the server, and the maximum verbosity level.
Handle to the
A handle representing a telemetry span, with the capability to enter the span if it exists.
Consensus DEBUG log level.
Consensus INFO log level.
Consensus TRACE log level.
Consensus WARN log level.
Substrate DEBUG log level.
Substrate INFO log level.
Span name used to report the telemetry.