Have you ever had a client call and tell you “your system is broken”? Of course you have. No further information, no directions to reproduce the issue.

It’s just broken.

You can pull the rest of the information out of your client, but you never really know if they might be missing some crucial detail or if the detail you need to find that bug is even something they would be able to tell you about. 


One of my favorite podcasts is Syntax and they keep banging on about one of their sponsors – LogRocket, so I thought I should check it out.
It’s an amazing piece of software that records users’ sessions and can give me a replay of what the user did prior to encountering an issue. This means I can see what they clicked on, what they entered into forms (except for really sensitive data – this can be customized) and I can see their network requests as well as the browser console.
This is all the stuff I usually use to debug an issue for a frontend system, so it’s really helpful that I can see it all.
I owe a huge thanks to the guys over at Syntax for introducing this amazing platform to their listeners.


Their quick start documentation helps you get started without much fuss. Since I love React and Redux, I also use their redux middleware. I also use LogRocket to identify session users so that they can be contacted if the need arises. 


As an added note, a day or two after I started using LogRocket, one of their evangelists connected with me on LinkedIn. I thought I might be the recipient of a sales pitch that would not be necessary but he just wanted to say hi and thank me for using their system and check that I am happy. LogRocket enables me to assist my customers before they even get a chance to report an issue to me and I can see that LogRocket has the same values in their team. Keep it up guys! 


LogRocket’s pricing can be found here. Their pricing strategy surprised me a bit. For a tool that provides so much value, I find the free plan to be more than enough for most of my needs at the moment – recording up to 1000 sessions and having a 14 day data-retention policy.
The free trial is fully unlocked for the first 14 days and then automatically switches to the free plan once your trial is over. For larger teams and projects, the Team plan (from $99/month) should really be more than enough, starting at 10 000 sessions and a one month retention policy. I’ve never found that bugs take weeks to get to me, so I don’t need such a huge retention policy.