Open mattgstevens opened 8 years ago
- registered new content
We can do this easiest by putting acreatedAt
timestamp in our Content records when we create them.
- registered new keypair
That's the same thing, I think. Add a createdAt
to Invoice records
- payment detected for content
We have this, the paymentTimestamp
- payment not detected for content
This is also data we have (or absence of it)
- influxdb as data store
Why should we use InfuxDB? It's fun to play with new tech and all, but adds a lot of overhead.
- would be good to see abandonments vs success (Invoice keypair made, but never isPaid)
This data we already have, can make a script to extract it into CSV at some point.
Does this ticket contain anything actionable that you want to do now?
ive used influxdb for metrics tracking in other projects, and would continue to use it with a dashboard like dashing
there is nothing im going to do today but i'd it is an important technical story to have metrics once core functionality is done
Ok. About adding another DB I'm wary - with risk of sounding boring, databases are not our secret sauce. Unsure about using Redis, as I don't really know how we would query it to get info like "what invoices were paid in the last week" or "what invoices were paid within 5 minutes of creation" without loading all data into app-land and then writing that functionality in Javascript. InfluxDB might be great but we both know how to do such things with Postgres/MariaDB.
I get it, and if we have to choose just one my vote is on Postgresql.
FWIW influxdb has an excellent query DSL for time related data (which user metrics and app metrics are) and are still something I'd like to do
So, the changes we need to implement to satisfy the bullets in your "Metrics" list are these:
createdAt
timestamp to Invoice record (unix timestamp? Should use some time lib for JS, since the standard Date lib is the worst)createdAt
timestamp to Content recordsWorking on this right now...
metrics:
Overall