As you’re Reading this blog, I assume you might be suffering from a common problem: noisy, low-value errors that make it harder for you and your team to define priorities on resolving the issues.

Noisy error chaos happens because browser JavaScript is complex to capture errors – because it’s not just one environment! There are so many browsers, JavaScript engines, operating systems, and browser extensions, all of which come together to make capturing good errors difficult.

One relatively simple approach is to simply hook into window.onerror and send that error information to the backend. Unfortunately, you won’t have any stack traces. Instead, onerror receives three parameters: message, the file, and line number.

window.onerror = function(message, file, line) {

    logError(file + ‘:’ + line + ‘\n\n’ + message);

};

Still, with the above code, you wouldn’t get the stack trace conveniently. Following the norms, the front-end source code is compressed with web pack, usually. That’s why we cannot capture your error stack trace.

Now assuming even if you have the stack-trace code, it wouldn’t give the liberty to identify and track the real cause of error your complex web application had. We faced such issues as well! It would be better if we can get information of what all actions user had taken at that time.

If you are already using Growlytics, whenever the user faces an issue, Growlytics captures errors and provides root cause analysis to the developers. But as you would know by now, capturing error doesn’t help every time.

In addition, Growlytics also capture all the user actions, input that leads to an issue. We capture live sessions, monitor user experience across several tiers, know what the customer has clicked, and see the malfunctioning pages. The visitor data is useful for diagnosing issues with the pages and show if all users all experiencing similar problems, or if it is the only single user affected. The aggregate looks at the calculation that gives a broad view of the application’s performance as a whole.

 

Integration of Stack trace, Request HTTP,  Line of Code (which are part of the root cause analysis of error debugging) and monitoring user’s activity simultaneously, almost zeroed down the probability of error troubling your team and helped them to fix the issues with ease. These features help the businesses to avoid bad user experience and gain competitive advantage.

 If you haven’t signed up on Growlytics yet, you must try it.. And yes, we have Forever Free subscription fee. If you have any queries, we’d love to hear from you.