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

Add Last Seen Time For Disconnected Node #774

Closed
13 of 14 tasks
m-janos opened this issue Feb 11, 2021 · 0 comments · Fixed by #790
Closed
13 of 14 tasks

Add Last Seen Time For Disconnected Node #774

m-janos opened this issue Feb 11, 2021 · 0 comments · Fixed by #790
Assignees

Comments

@m-janos
Copy link
Contributor

m-janos commented Feb 11, 2021

  • I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

  • When Multichain node is disconnected, display last active timestamp
  • Find the way how to retrieve the time value
  • Screen --> component: e.g. http://localhost:3000/nodes --> Network

  • 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 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?

Parent Task 🔗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants