Technology RadarTechnology Radar

Client-Side Error Logging

architecturefrontend
This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.
Adopt

Updated to adopt.

Trial

More and more business logic is done client-side with various web and app technologies. How do we know if everything works in production? We can easily track backend exceptions in the server logs, but what about client-side errors in the user's browser or mobile app?

With client-side error logging, we send errors to a central server to see instantly what is going wrong. With this method errors can be found and resolved quickly before they affect even more users.

At AOE, we use the Open Source solution Sentry.io. It can handle multiple projects and teams and integrates well with other services such as Mattermost/Slack and Issue Tracking Systems.