Metrics

[Nixotica]

It would be nice to have a basic system for tracking metrics in code like user settings and interactions so we can better find out issues early on. They don't need to be per-user but aggregated metrics would be interesting. Even if we don't have anything modifiable by the user like settings, we can track early on edge cases in code.

Whatever we end up doing, we need to ensure we set it up so that we can aggregate metrics across a defined time period we set in code per-metric or metric type, as well as a service that allows us to interface with our metrics (Kibana? or something with better metric math).

[sethhargis28]

It would be nice to have this for design reasons too - see what frustrates players, what engages them, etc. I could come up with a basic list of metrics for that, including something to track player retention as well as other useful stuff

[mworzala]

We had an extremely brief comment about this a while back. I am a fan of ES/Kibana, although it may be a bit overkill to start. In any case I think that we should setup some reasonable common api to track various metrics.

Prometheus and Grafana are also not to be ignored. I think they should be used for system metrics at a minimum, but if we are only tracking aggregate metrics then we can probably use them for all of the metrics.