We aren't tracking client side errors anywhere right now. This makes it hard to debug certain issues that users come across unless they are technical enough to open dev tools and screenshot the error messages.
I threw the question to Claude/Anthropic, and it suggested tools like Sentry, LogRocket, TrackJS, or Rollbar, all of which I assume work something like Google Analytics, where logs are sent to them, and they provide a dashboard to look through them. I think that they all have some sort of free tier, and then you'd need to pay after some number of errors being logged (something like 1k-5k errors). Open Telemetry was the truly free solution suggested, which I believe just captures listens for appropriate errors, and then we'd log those to our own back end.
I didn't spend much time looking, so we should do some more research!
A week later and I have another bug report from a user that only has a client-side error that I can't see. More reason to get something like this set up!
We aren't tracking client side errors anywhere right now. This makes it hard to debug certain issues that users come across unless they are technical enough to open dev tools and screenshot the error messages.
I threw the question to Claude/Anthropic, and it suggested tools like Sentry, LogRocket, TrackJS, or Rollbar, all of which I assume work something like Google Analytics, where logs are sent to them, and they provide a dashboard to look through them. I think that they all have some sort of free tier, and then you'd need to pay after some number of errors being logged (something like 1k-5k errors). Open Telemetry was the truly free solution suggested, which I believe just captures listens for appropriate errors, and then we'd log those to our own back end.
I didn't spend much time looking, so we should do some more research!