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

Metrics server should return a metrics rate value #374

Closed
futurechimp opened this issue Oct 12, 2020 · 0 comments · Fixed by #403
Closed

Metrics server should return a metrics rate value #374

futurechimp opened this issue Oct 12, 2020 · 0 comments · Fixed by #403
Assignees
Milestone

Comments

@futurechimp
Copy link
Contributor

At the moment, we've hardcoded the duration for metrics reporting. This causes trouble for us when node numbers increase, because the metrics server gets hammered if we expand the network significantly. Although metrics are not part of our security model (they're self-reported), they're still pretty useful for people to see whether their nodes are up and running.

Let's define the metrics reporting_period dynamically, where reporting_period = num_mixnodes / desired_traffic_rate. If we say we want to have e.g. a desired_traffic_rate of 50 requests per second hit the metrics API, and we have right now 600 mixnodes, then our reporting_period ends up being 30 seconds. Every time a mixnode submits a metrics report, it gets back the reporting_period of 30. When the network grows or shrinks, nodes will automatically adjust to send their traffic at lower or higher rates depending on what the metrics server can support.

@futurechimp futurechimp added this to the 0.9.0 milestone Oct 12, 2020
@futurechimp futurechimp added this to Backlog in Core systems via automation Oct 12, 2020
@jstuczyn jstuczyn self-assigned this Oct 14, 2020
Core systems automation moved this from Backlog to Done Oct 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Core systems
  
Done
Development

Successfully merging a pull request may close this issue.

2 participants