You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, I want to be able to configure my node to submit to SubVT Telemetry, so that I can receive notifications about the real-time off-chain data about my validator and take required action where necessary.
Users will be able to optionally configure SubVT Telemetry for their validator node after they add the node to their validator list. Substrate nodes support multiple telemetry targets, so a user may choose to keep their current telemetry settings and add SubVT on top of the existing configuration.
Implementation Details
SubVT Telemetry doesn't have to have a public front-end. SubVT backend communicates with the telemetry instance through websockets and takes action where necessary. We also may need to extend the Substrate Telemetry code to push indexed data into the SubVT database for historical access.
The text was updated successfully, but these errors were encountered:
User story
Feature Details
Figure 6.1 Validator node adds SubVT Telemetry in node startup command.
Users will be able to optionally configure SubVT Telemetry for their validator node after they add the node to their validator list. Substrate nodes support multiple telemetry targets, so a user may choose to keep their current telemetry settings and add SubVT on top of the existing configuration.
Implementation Details
SubVT Telemetry doesn't have to have a public front-end. SubVT backend communicates with the telemetry instance through websockets and takes action where necessary. We also may need to extend the Substrate Telemetry code to push indexed data into the SubVT database for historical access.
The text was updated successfully, but these errors were encountered: