Open josephwegner opened 9 years ago
Sorry if this is the wrong place for this idea... it doesn't seem like something that CommonWeb would necessarily be concerned with, but it seemed like too specific of an idea to email to contact@. Let me know if I should move this discussion elsewhere.
I love this idea. @dustinlarimer cooked up something once along these lines and might have valuable information to share.
I do think this fits into the ethos of common-web, the ethos defined broadly as "auto-collect interesting things happening on web pages" :)
@josephwegner that's a pretty rad project! I made a basic error catcher for keen here: https://gist.github.com/dustinlarimer/9908181
That looks awesome! Pretty much exactly what I was thinking!
On Thu, Mar 19, 2015, 6:27 PM Dustin Larimer notifications@github.com wrote:
@josephwegner https://github.com/josephwegner that's a pretty rad project! I made a basic error catcher for keen here: https://gist.github.com/dustinlarimer/9908181
— Reply to this email directly or view it on GitHub https://github.com/keen/common-web/issues/18#issuecomment-83802364.
I would love to run something like this on keen-web so we can get ahead of things breaking if/when new browser versions roll out.. had that happen with a fun Firefox CORS update last summer. Are there any other open projects for exposing errors? Maybe we can tap into something with a recipe?
Track.js is the best that I know about. HoneyBadger also has a JavaScript SDK, but it requires manually catching things.
Its a hard problem, because onerror
provides such terrible output.
On Thu, Mar 19, 2015, 6:54 PM Dustin Larimer notifications@github.com wrote:
I would love to run something like this on keen-web so we can get ahead of things breaking if/when new browser versions roll out.. had that happen with a fun Firefox CORS update last summer. Are there any other open projects for exposing errors? Maybe we can tap into something with a recipe?
— Reply to this email directly or view it on GitHub https://github.com/keen/common-web/issues/18#issuecomment-83812815.
OK, so this idea has been marinating for a few days.
Check out http://trackjs.com/
I'm not sure if it's something that would be built in to CommonWeb, but error tracking seems like a really sweet use case for someone using Keen. You can pass in pretty rich error objects (see Honeybadger's payload for an example), and then you could create a user timeline of which events CommonWeb picked up before that error got triggered.
Visualizing that error well (how TrackJS does it) would be a pain in the bones, but it could be super powerful. You could do all kinds of queries slicing users to see which errors affect them, how errors have trended over time, which errors have the biggest affect on conversion funnels, etc.
(for the record, I actually think error tracking is a really cool idea, even outside of browserland. Tracking ruby/node/java/anything errors with Keen seems super powerful).