mirror of https://github.com/pezkuwichain/pezkuwi-telemetry.git synced 2026-05-06 21:47:59 +00:00

Files

T

James Wilson fe19a75414 Un-brittle-ify backend E2E tests and have them run by default again in CI (#397 )

* test running tests

* Add delay so that core knows about node before feed subscribes to limit chance of race

* move delaye to the right place

* Don't do expensive docker step untill we will be pushing the image

* docker test skipped as hoped, so push to 'true'

* just remove docker steps in github CI entirely since they aren't needed by anything (gitlab CI does this stuff now)

* run CI on pull requests too to catch PRs from forks

2021-09-06 11:30:17 +01:00

common

Flume fix part 2: avoid using flume in a couple of cases, and revert attempted fix#1 (#396 )

2021-09-03 15:55:25 +01:00

docs

Tweak docker(compose) files (can't test them yet) and add a little backend documentation

2021-07-05 10:26:32 +01:00

telemetry_core

Un-brittle-ify backend E2E tests and have them run by default again in CI (#397 )

2021-09-06 11:30:17 +01:00

telemetry_shard

Avoid using flume::Receiver::into_stream() to avoid memory leaks until the issue is resolved upstream (#394 )

2021-09-03 08:40:43 +01:00

test_utils

Flume fix part 2: avoid using flume in a couple of cases, and revert attempted fix#1 (#396 )

2021-09-03 15:55:25 +01:00

.dockerignore

Tweak docker(compose) files (can't test them yet) and add a little backend documentation

2021-07-05 10:26:32 +01:00

Cargo.lock

Avoid using flume::Receiver::into_stream() to avoid memory leaks until the issue is resolved upstream (#394 )

2021-09-03 08:40:43 +01:00

Cargo.toml

use ws_client in shard, too, and make it better at handling core disconnecting

2021-07-20 13:04:10 +01:00

Dockerfile

Hardening of the Backend docker image (#379 )

2021-08-26 14:32:11 +02:00

README.md

make it obvious that unbounded channels don't need to await, and tidy up some bits

2021-07-12 10:01:23 +01:00

README.md

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.