mirror of
https://github.com/pezkuwichain/pezkuwi-telemetry.git
synced 2026-04-30 21:18:01 +00:00
Alexandru Vasile
4378fd2192
* frontend: Update package lock Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * frontend/stats: Format linux kernel version Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Add [64; 128) RAM bucket Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Parse kernel string to include only version numbers The linux kernel version string is parsed to include only the kernel version, major version and minor version. Ignoring the patch number and kernel specific info leads to a better aggregation of data. Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Fix typo Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * core: Add CPU vendor to reported chain stats Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * frontend: Propagate CPU vendor to UI Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Parse kernel version by `+` Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Add CPU vendors and ignore ascii case Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * Revert "frontend/stats: Format linux kernel version" This reverts commit 411b9a4ceef9c664816404eaee1fb64f61fe85b3. * backend: Fix plus sign test Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Trim kernel versions Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> * backend: Modify cpu_vendor Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io> --------- Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
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.