Web error handling concept
Table of content
Conclusion
With this concept, we have developed an infrastructure to safely handle errors while maintaining enough information to fix occurring errors.
The important points from this post are:
Separate error details for developers and error details for the frontend
Log errors that occur with additional helpful information
Give the frontend enough information to present an error message to the user
Of course, this is just a basic concept, which works in practice, but can be enhanced and adapted to your individual needs.
An example for improving this concept would be a separation of "normal errors," which are just logged, and "critical errors," which could trigger something like an alarm email to the developer.
Feel free to adapt this concept and have fun becoming creative while developing!