over budget
Monitoring solution for a node
Current Project Status
unfunded
Total
amount
Received
$0
Total
amount
Requested
$23,000
Total
Percentage
Received
0.00%
Solution

Estamos desarrollando una solución cliente/servidor para hacer un seguimiento de los parámetros clave del nodo/servidor y enviar notificaciones a una aplicación especial de operador de nodo

Problem

La mayoría de los SPO utilizan gLiveView para seguir el estado de los nodos (requiere acceso a la línea cmd) o prometheus/graphana, donde faltan datos esenciales

Addresses Challenge
Feasibility
Auditability

Nosotros

3 members

  • download
  • download

Detailed Plan

Our solution will provide easy to use monitoring toolset for SPO (especially single SPO) and as a result, it will improve the overall Cardano network security and reliability, and here is why

- solution increases awareness about the node state
- provides the possibility to check the node state on the go without access to PC or Mac
- setup and tune any custom alerts to cover your own monitoring needs
- immediate notifications to multiple destinations in case of any alert is triggered

Solution components: controller, informer, alerter, mobile app

Usage

- install controller and alerter component to any Linux server (can be one of the relays)
- install informer component on every physical node (block producer or relay) and connect them to the controller
- install the mobile app and configure it to connect to the controller

That’s it!

We already started development and doing it already 6 month and have a working prototype but we need more resources to finalize our solution, we are planning to do the following

- develop mobile/desktop node monitoring app for a node operator
- develop a one-button-click installer for the already developed server components
- develop web application to customize alerts
- develop storing the monitoring data to DB for the future analysis
- cover solution with automatic tests (optionally, if we cover other items in this list)
- develop telegram bot as an additional channel for notifications
- setup and test basic end-to-end notifications for mobile app and telegram
- publish the app in Google Play / App Store

Current developments are already available to the public and are located on GitHub (https://github.com/orgs/adarocket)

Advantages compared to current node monitoring tools

- monitoring node parameters and availability on the go in mobile application
- immediate notifications to the mobile app in case if something goes wrong (or right :)
- customizable parameters for the notification with flexible tuning
- sparing resources client (informer is quite a tiny app and takes minimum resources to run)
- quick and reliable data protocol for communicating between the solution components (gRPC)

Technical overview

- all server components are developed with Go (golang) and can be installed in minutes
- the mobile app will be developed using Flutter and be available on iOS/Android/Mac/Windows/Linux
- communication protocol between the components is gRPC
- server components will be tested on Debian
- database to store historical monitoring data: Postgres
- our solution is open source and will stay forever

We will need from 3 to 6 months to finalize all the components and deliver the mobile app.

Publishing mobile applications on the Apple AppStore and Google Play Store will be the sign of delivering a solution (but not the end, we still have plenty of ideas and we will continue the development of the solution in the future after all the things above are implemented)

We will be glad if the SPO community will use our solution to monitor their nodes, we hope that we will have hundreds of users

Possible delivery date: May 1, 2022
The possible delivery date for alpha users: March 1, 2022

As we are managing our own node (BLACK), we are already using our solution to monitor the node, we will be the first who will use and test the new components and mobile app, and we surely understand the need for SPO.

Reseñas de CAs (1)

Comments

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00