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

Node telemetry #2225

Open
zhyatt opened this issue Aug 17, 2019 · 7 comments
Open

Node telemetry #2225

zhyatt opened this issue Aug 17, 2019 · 7 comments
Milestone

Comments

@zhyatt
Copy link
Member

@zhyatt zhyatt commented Aug 17, 2019

Provide methods for nodes to send various metrics between each other for better monitoring of network status and upgrades progress. Some metrics being considered:

  • Block count
  • Cemented block count
  • Set bandwidth cap
  • Protocol version number
  • Node vendor version
  • Peer counts

Are there any other metrics to consider for inclusion?

@zhyatt zhyatt added this to the V21.0 milestone Aug 17, 2019
@wezrule

This comment has been minimized.

Copy link
Collaborator

@wezrule wezrule commented Aug 17, 2019

Perhaps number of accounts

@schenkty

This comment has been minimized.

Copy link
Contributor

@schenkty schenkty commented Aug 18, 2019

@wezrule I assume you are referring to number of accounts in the node wallet? If so, I think it is a very slippery slope to include any wallet data. It may be too precautionary but anything along the lines of sending wallet data to peers could have a mistake at some point where private wallet data is leaked to a peer which concerns me.

@wezrule

This comment has been minimized.

Copy link
Collaborator

@wezrule wezrule commented Aug 18, 2019

I am referring to the number of the accounts in the ledger

@schenkty

This comment has been minimized.

Copy link
Contributor

@schenkty schenkty commented Aug 18, 2019

@wezrule oh thank you. I was worried 😂

@arranHarty123

This comment has been minimized.

Copy link

@arranHarty123 arranHarty123 commented Aug 22, 2019

Would bootstrap settings be useful? e.g. my node is not bootstrapping anyone, but will establish x bootstrap connections to catch up.

@zhyatt

This comment has been minimized.

Copy link
Member Author

@zhyatt zhyatt commented Oct 14, 2019

Related to #1308

@bryanwag

This comment has been minimized.

Copy link

@bryanwag bryanwag commented Nov 1, 2019

It is crucial to have a reliable and objective way to measure node performance because the scalability of the network depends heavily on node hardware, yet we currently have to rely on rep's self-report and stress tests to even get a basic idea on that metric. This method is neither quantitative nor reliable. Thus, it's easy to game and hard to educate users on how to choose a rep that is beneficial to the network.

If we allow each peer to report vote latency of other peers (time(Rep A vote arrives) - time(quorum reached)) and aggregate this result, with appropriate statistical modeling we can quantitatively and reliably measure the performance of reps.

I'm not a dev and not sure whether vote latency can/should be reported by peers within the node software. If this is the wrong place please let me know. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.