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

Fix typos and change some grammatical constructions

Browse Source
This commit is contained in:
daniel.motzko
2021-07-02 14:27:33 +02:00
parent 80526bedd1
commit 4f670a98c0
15 changed files with 91 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,8 +4,12 @@ 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?
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.
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 Mattermost/Slack and Issue Tracking Systems.
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 Mattermost/Slack and Issue Tracking Systems.