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
check if chain connection/permission ready (this applies to not yet connected nodes, on which logging should not even run)
getpeerinfo issued from api returns an array of connected nodes
process the array (we do not need all the information)
Create an event e.g. store_network_infromation or such
Condition: Check if the event for that day is written in the stream
if not, store the event in stream
YYYYMMDD as key
possibly use addresses of nodes as additional keys?
use also the address of publishing node in keys
which stream? events in "nodes" are expected to have certain structure and function (get in Nodes.ts) => consult with Stefan (using network_log atm)
all nodes registered in the chain are in the nodes stream. if some of these nodes are not connected to the chain (getpeerinfo returns array with some of them missing), API should take care of this -> look in the stream when was that particular node last seen, and include the information in the reply to frontend
Frontend gets the information from API - maybe piggyback response in such a way that no breaking change occurs?
Summary 💡
Process runs every 24H on every API
check if chain connection/permission ready (this applies to not yet connected nodes, on which logging should not even run)
getpeerinfo
issued from api returns an array of connected nodesprocess the array (we do not need all the information)
Create an event e.g.
store_network_infromation
or suchCondition: Check if the event for that day is written in the stream
if not, store the event in stream
YYYYMMDD as key
possibly use addresses of nodes as additional keys?
use also the address of publishing node in keys
which stream? events in "nodes" are expected to have certain structure and function (get in Nodes.ts) => consult with Stefan (using
network_log
atm)all nodes registered in the chain are in the nodes stream. if some of these nodes are not connected to the chain (
getpeerinfo
returns array with some of them missing), API should take care of this -> look in the stream when was that particular node last seen, and include the information in the reply to frontendFrontend gets the information from API - maybe piggyback response in such a way that no breaking change occurs?
Parent Task 🔗
The text was updated successfully, but these errors were encountered: