Client-side logging brings the great error management platform from the server, directly into the user's browser. All uncaught errors are automatically picked up and enriched with detailed information about the environment. Everything is shipped to elmah.io, where notifications, searching, and managing errors just work.
Errors can be stored in your existing or a dedicated client-side error log. In both scenarios both email notifications as well as our integrations to Slack and Microsoft Teams works out of the box. You already set up your organization and team members, why configuring who needs notifications on client-side errors, requires a few mouse clicks only.
Having both the client and the server's perspective will reduce the time you need to spend on bug fixing. Time that you will be able to spend on adding new features to your now zero-known-bugs product.
With elmah.io's Smart Grouping feature, errors are bundled in groups, showing you the unique errors happening and the severity of each error. Unlike similar products out there, elmah.io logs every single error. This makes debugging a lot easier since you can browse through each error instance within a group, rather than looking at a simple counter.
With elmah.io's Device Insights, you will receive detailed information about the environment generating the error. Being able to see if an error is generated from a desktop or mobile browser and even the orientation of the screen, will make it a lot easier to re-create an error.
You are already following good practices by bundling and minifying your scripts. While browsers will love you for doing that, the errors generated by your application won't. Bundled and minified stack traces, make it impossible to find the actual line of code causing an error.