Of course, you could record timing metrics with addCustomEvent but what's the fun in that? Having a separate data format for timers (should) makes it easier to parse this data on the back end.
This pull request:
Adds a method to put timing data in StatsStore
Adds methods for storing/retrieving timing data from the database
Adds unit tests for new functionality
updates the README to document the new methods and clean up some cruft
Future work:
Make sure the database doesn't start to balloon in size
Make sure requests don't start ballooning in size
Make Atom metrics package actually send timing data
Addresses https://github.com/atom/telemetry/issues/13
Of course, you could record timing metrics with
addCustomEventbut what's the fun in that? Having a separate data format for timers (should) makes it easier to parse this data on the back end.This pull request:
StatsStoreFuture work:
metricspackage actually send timing data