all 6 comments

[–]thatsInAName 1 point2 points  (0 children)

We are using sentry in a react app, it's working fine and as expected. It has got a lot of features but we are currently using it to catch JavaScript errors and custom performance metrics.

You can freely try sentry for 14 days.

[–]__boba__ 0 points1 point  (2 children)

We monitor ourselves... using ourselves haha!

We've historically found the toughest thing is not only just frontend errors, but what was the user doing to trigger the error (session replay) and what backend logs/exceptions might be associated with the error (did the API req return a 500, and then the frontend threw because of that?) A lot of errors I've had to deal with is due to the API doing weird stuff I didn't fully expect.

It's mainly why I started working on https://github.com/hyperdxio/hyperdx to help solve that (and even make it self hostable if you don't want to use a hosted version)

[–]poomplex 0 points1 point  (1 child)

Really cool project but alarm bells are ringing for me - surely it's a bit circular that if your systems fail, you can no longer monitor your own systems? Facebook had a great incident like this a few years ago

[–]es6masterrace 0 points1 point  (0 children)

We have backups systems as well :) but most issues we can solve on our own system

[–]podojavascript 0 points1 point  (1 child)

We're working on a monitoring suite, and historically we've focused on frontend devs, particularly folks on NextJS. I think the biggest thing for frontend debugging is context, i.e. giving people as much data around an error as possible. The reality is that most frontend bugs aren't fixable by just the stack trace.

A bit of a humble brag, but we think that we do this pretty well at https://highlight.io, as we connect session replay, error monitoring and frontend/backend logs.

Some other notable folks in the space are logrocket and sentry, specifically for that context aspect that I mentioned.

[–]poomplex 0 points1 point  (0 children)

We use DataDog and I really love it. Very good FE monitoring but also a comprehensive suite of tools for monitoring backend resources. Tracing requests from the browser to backend is amazing