mirror of
https://github.com/pezkuwichain/pezkuwi-telemetry.git
synced 2026-04-24 20:38:01 +00:00
James Wilson
7a3e30cb01
* Only remove the feed that disconnected to not break the rest... * use multimap struct to avoid sync issues between feed and chain * add a remove test, too * cargo fmt * fix name of test * move multimap to common so we can doctest it and add 'unique' to name * cargo fmt * Return old key if value moved to make uniqueness more obvious
Backend Crates
This folder contains the rust crates and documentation specific to the telemetry backend. A description of the folders:
- telemetry_core: The Telemetry Core. This aggregates data received from shards and allows UI feeds to connect and receive this information.
- telemetry_shard: A Shard. It's expected that multiple of these will run. Nodes will connect to Shard instances and send JSON telemetry to them, and Shard instances will each connect to the Telemetry Core and relay on relevant data to it.
- common: common code shared between the telemetry shard and core
- test_utils: Test utilities, primarily focused around making it easy to run end-to-end tests.
- docs: Material supporting the documentation lives here
Architecture
As we move to a sharded version of this telemetry server, this set of architecture diagrams may be useful in helping to understand the current setup (middle diagram), previous setup (first diagram) and possible future setup if we need to scale further (last diagram):
Deployment
A Dockerfile exists which builds the Shard and Telemetry Core binaries into an image. A docker-compose.yaml in the root of the repository can serve as an example of these services, along with the UI, running together.