Keen.io looks awesome! I just spent a coupla' minutes skimming their docs and stuff.
However, even though it uses a "persistent connection" it's still a HTTPS POST over the network every time it needs to send something. Blocking too. Perhaps it's doable to "up" that to be a gevent greenlet or something so it can send async but that's probably not trivial.
As far as bloat is concerned, I think this is where it matters. I use my eventlog only to send events when users do something that relates to changing the state (e.g. doing a POST) so there aren't that many events actually.
We started with something like this, but ended up not liking the DB bloat that this sort of thing causes. We also started finding that we were using our event log data for some light analytics, which isn't something we had anticipated.
After pondering a number of alternative methods (breaking the event log out into its own DB was the leading candidate), we discovered Keen.io. You throw event logs at it and you can do all kinds of filtering/graphing/statistical calculations based on the key/value pairs within each body.
I don't work for Keen.io, but we really love it at Pathwright. Avoids a lot of unnecessary DB writes and DB bloat, plus our less technical business staff can still figure out how to query it without involving a developer.
Comment
Keen.io looks awesome! I just spent a coupla' minutes skimming their docs and stuff.
However, even though it uses a "persistent connection" it's still a HTTPS POST over the network every time it needs to send something. Blocking too. Perhaps it's doable to "up" that to be a gevent greenlet or something so it can send async but that's probably not trivial.
As far as bloat is concerned, I think this is where it matters. I use my eventlog only to send events when users do something that relates to changing the state (e.g. doing a POST) so there aren't that many events actually.
Parent comment
We started with something like this, but ended up not liking the DB bloat that this sort of thing causes. We also started finding that we were using our event log data for some light analytics, which isn't something we had anticipated. After pondering a number of alternative methods (breaking the event log out into its own DB was the leading candidate), we discovered Keen.io. You throw event logs at it and you can do all kinds of filtering/graphing/statistical calculations based on the key/value pairs within each body. I don't work for Keen.io, but we really love it at Pathwright. Avoids a lot of unnecessary DB writes and DB bloat, plus our less technical business staff can still figure out how to query it without involving a developer.