Rethinking front-end error reporting

by jastron 1/17/2018, 6:49:38 PM with 9 comments
  • by bryanrasmussenon 1/17/2018, 8:22:38 PM

    So, we've logged everything the user has done into logrocket, and given logrocket some way of uniquely identifying the user.

    So anyone should ask, what is the GDPR impact here?

  • by randallon 1/17/2018, 8:17:39 PM

    I feel weird... like I've never heard of this before and it seems fully built out... what am I missing?

  • by ro-larenon 1/17/2018, 6:59:52 PM

    We built a similar system internally that accomplished some of these functions. Essentially data is ingested to an ELK cluster with some custom views on top. This definitely looks more polished though!

  • by salt-lickeron 1/17/2018, 7:19:16 PM

    I've used TrackJS in the past - they have context on the user session surrounding front-end exceptions, e.g. what the user clicked on beforehand. Is a video replay really that much more useful?

  • by mrjaegeron 1/17/2018, 9:01:26 PM

    Very cool! Do you know if this product is currently HIPAA compliant or if there are plans to make it so in the future?

  • by simplifyon 1/17/2018, 8:41:50 PM

    How does this compare to fullstory.com?

  • by txmjson 1/17/2018, 10:42:37 PM

    Are you still planning on releasing an open source version of LogRocket, much like Sentry offers one?

  • by yomieluon 1/17/2018, 7:43:23 PM

    I see this will log Redux actions/state leading up to a crash- can it also log data from MobX?

  • by seattle_springon 1/17/2018, 10:01:43 PM

    Does LogRocket easily hook up to PagerDuty?