Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metrics #24

Open
mattgstevens opened this issue Apr 10, 2016 · 8 comments
Open

Metrics #24

mattgstevens opened this issue Apr 10, 2016 · 8 comments

Comments

@mattgstevens
Copy link
Member

metrics:

  • registered new content
  • registered new keypair
  • payment detected for content
  • payment not detected for content

Overall

  • would be good to know IP, see where our producers / consumers are coming from
  • some kind of dashboard => mixpanel
  • influxdb as data store
  • would be good to see abandonments vs success (Invoice keypair made, but never isPaid)
@fromheten
Copy link
Member

fromheten commented Apr 12, 2016

  • 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)

@fromheten
Copy link
Member

  • 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.

@fromheten
Copy link
Member

Does this ticket contain anything actionable that you want to do now?

@mattgstevens
Copy link
Member Author

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

@fromheten
Copy link
Member

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.

@mattgstevens
Copy link
Member Author

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

@fromheten
Copy link
Member

So, the changes we need to implement to satisfy the bullets in your "Metrics" list are these:

  • Add createdAt timestamp to Invoice record (unix timestamp? Should use some time lib for JS, since the standard Date lib is the worst)
  • Add a createdAt timestamp to Content records

@fromheten
Copy link
Member

Working on this right now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants