Redesign metrics #148
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
The current design makes it hard to add some metrics keys, including
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.
The text was updated successfully, but these errors were encountered: