Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] #4 - Notification settings #10

Open
kukabi opened this issue Jul 26, 2021 · 0 comments
Open

[Feature] #4 - Notification settings #10

kukabi opened this issue Jul 26, 2021 · 0 comments

Comments

@kukabi
Copy link
Member

kukabi commented Jul 26, 2021

User story

As a user, I want to be able to configure the notifications I want to receive about my validators, possibly on different Substrate networks, and on what channels to receive them, so that I can take action when required, or just get to know in real-time when certain events happen.


Feature Details


Figure 4.1 SubVT configurable notification types.

Notifications can be received via email, push notifications, and for urgent events SMS and GSM. User is free to configure notifications for any of the following events.

  • New nominator, or the change of the amount nominated from an existing nominator.
  • Loss of a nominator.
  • Offline offense, and the resulting chilling event.
  • Voluntary chilling of a validator.
  • Session keys change.
  • Commission change.
  • Active set inclusion and exclusion.
  • Block authorship.
  • Unclaimed payouts after a configurable x hours/sessions/eras.

Notifications related to Telemetry data if configured:

  • Node behind by a configurable x blocks.
  • Peer count below a configurable x peers.
  • Offline for a configurable x seconds/minutes.
  • More than a configurable x transactions in queue.
  • Binary version out-of-date.
  • Binary version change.

Network- and program-specific notifications, such as 1KV for Polkadot and Kusama:

  • Rank change.
  • Validity change.
  • New fault.
  • Score class change (A, B, C etc.)

Exact design details are not clear yet, but one approach under consideration is by defining rules and parameters.


Figure 4.2 A rule-based approach to notification configuration.

Implementation Details

SubVT backend scans every new finalized block and observes the SubVT Telemetry instance continuously and notifies the node operators according to the pre-defined notification rules.


Figure 4.3 Notification system overall view.

@kukabi kukabi self-assigned this Jul 26, 2021
@kukabi kukabi removed their assignment Jul 26, 2021
@kukabi kukabi changed the title [Feature] Notification settings [Feature] #4 - Notification settings Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant