Files
pezkuwichain 267fcec12d fix: quick-checks CI failures - taplo format, zepter, umbrella
1. TOML format (taplo): 123 files reformatted using correct config
   - Command: taplo format --config .config/taplo.toml

2. Zepter feature propagation fix:
   - pezframe-support: added pezsp-timestamp/try-runtime to try-runtime feature

3. generate-umbrella.py bug fix:
   - Script crashed when Cargo.toml/src didn't exist in umbrella dir
   - Added existence checks before deletion
2026-01-26 00:39:59 +03:00
..

pezsc-telemetry

Bizinikiwi's client telemetry is a part of Bizinikiwi that allows ingesting telemetry data with for example PezkuwiChain telemetry.

It works using Tokio's tracing library. The telemetry information uses tracing's logging to report the telemetry data which is then retrieved by a tracing Layer. This layer will then send the data through an asynchronous channel to a background task called [TelemetryWorker] which will send the information to the configured remote telemetry servers.

If multiple Bizinikiwi nodes are running in the same process, it uses a tracing::Span to identify which Bizinikiwi node is reporting the telemetry. Every task spawned using pezsc-service's TaskManager automatically inherit this span.

Bizinikiwi's nodes initialize/register with the [TelemetryWorker] using a [TelemetryHandle]. This handle can be cloned and passed around. It uses an asynchronous channel to communicate with the running [TelemetryWorker] dedicated to registration. Registering can happen at any point in time during the process execution.

License: GPL-3.0-or-later WITH Classpath-exception-2.0