from Hacker News

Rethinking front-end error reporting

by jastr on 1/17/18, 6:49 PM with 28 comments

  • by bryanrasmussen on 1/17/18, 8:22 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 randall on 1/17/18, 8:17 PM

    I feel weird... like I've never heard of this before and it seems fully built out... what am I missing?
  • by ro-laren on 1/17/18, 6:59 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-licker on 1/17/18, 7:19 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 mrjaeger on 1/17/18, 9:01 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 simplify on 1/17/18, 8:41 PM

    How does this compare to fullstory.com?
  • by txmjs on 1/17/18, 10:42 PM

    Are you still planning on releasing an open source version of LogRocket, much like Sentry offers one?
  • by yomielu on 1/17/18, 7:43 PM

    I see this will log Redux actions/state leading up to a crash- can it also log data from MobX?
  • by seattle_spring on 1/17/18, 10:01 PM

    Does LogRocket easily hook up to PagerDuty?