I just want to lay out some thoughts about statistics.
There's of course different scopes of statistics I'd like to collect. There's hourly (maybe even shorter?) with number of players online and number of servers. There's daily, such as downloads, again number of people coming online, etc. When it gets a bit complicated is weekly. We could either derive weekly statistics from the past 7 days, or we could have a reset at the end of each week.
Since what stats are collected is a fairly variable thing (for example, right now we might only be track number of downloads, but we might add in number of updates later), I think a table like the following would be ideal:
date
scope
data
scope being "hourly", "daily", etc. and data would just be a json string of whatever data there is. This allows the system to be incredibly flexible.
I just want to lay out some thoughts about statistics.
There's of course different scopes of statistics I'd like to collect. There's hourly (maybe even shorter?) with number of players online and number of servers. There's daily, such as downloads, again number of people coming online, etc. When it gets a bit complicated is weekly. We could either derive weekly statistics from the past 7 days, or we could have a reset at the end of each week.
Since what stats are collected is a fairly variable thing (for example, right now we might only be track number of downloads, but we might add in number of updates later), I think a table like the following would be ideal:
date scope data
scope being "hourly", "daily", etc. and data would just be a json string of whatever data there is. This allows the system to be incredibly flexible.