AJR/TechRadarAJR
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Copy items that are not faded out

Browse Source
This commit is contained in:
Daniel Pötzinger
2017-09-08 22:58:47 +02:00
parent 8be44ec001
commit c5e09dd126
63 changed files with 2 additions and 645 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
radar/2017-10-01/client-side-error-logging.md
View File

@@ -4,9 +4,3 @@ ring: trial
quadrant: methods-and-patterns
---
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](https://sentry.io/welcome/).io. It can handle multiple projects and teams and integrates well with other services such as Mattemost/Slack and Issue Tracking Systems.