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

Redesign metrics #148

Open
2 tasks
ordovicia opened this issue Mar 19, 2019 · 0 comments
Open
2 tasks

Redesign metrics #148

ordovicia opened this issue Mar 19, 2019 · 0 comments
Assignees
Labels
api Area: API for users breaking change Importance: Design and implementations that break existing user programs high priority Importance: High priority metrics Area: Metrics of simulation results needs decision Importance: in need of decision

Comments

@ordovicia
Copy link
Collaborator

ordovicia commented Mar 19, 2019

The current design makes it hard to add some metrics keys, including

  • Slowdown of each pod
  • Duration took for each operation in the simulator (e.g. scheduleOne() function)

My proposal is to switch the design to use a global metrics server, so that from any code location we can register and update a pair of metrics key and value.

@ordovicia ordovicia added api Area: API for users metrics Area: Metrics of simulation results labels Mar 19, 2019
@ordovicia ordovicia self-assigned this Mar 19, 2019
@ordovicia ordovicia added needs decision Importance: in need of decision high priority Importance: High priority breaking change Importance: Design and implementations that break existing user programs labels Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Area: API for users breaking change Importance: Design and implementations that break existing user programs high priority Importance: High priority metrics Area: Metrics of simulation results needs decision Importance: in need of decision
Projects
None yet
Development

No branches or pull requests

1 participant