Errors – Do you know the daily process to improve the health of your web application?

Last updated by Brady Stroud [SSW] about 1 month ago.See history

Application Insights can provide an overwhelming amount of errors in your web application, so use just-in-time bug processing to handle them.

The goal is to each morning check your web application's dashboard and find zero errors. However, what happens if there are multiple errors? Don't panic, follow this process to improve your application's health.

App Insights Failures
Figure: Every morning developers check Application Insights for errors

Once you have found an exception you can drill down into it to discover more context around what was happening. You can find out the user's browser details, what page they tried to access, as well as the stack trace (Tip: make sure you follow the rule on How to set up Application Insights to enhance the stack trace).

App Insights Failures drilldown
Figure: Drilling down into an exception to discover more.

It's easy to be overwhelmed by all these issues, so don't create a bug for each issue or even the top 5 issues. Simply create one bug for the most critical issue. Reproduce, fix and close the bug then you can move onto the next one and repeat. This is just-in-time bug processing and will move your application towards better health one step at a time.

20 08 2014 12 04 31 PM compressor
Figure: Bad example - creating all the bugs

20 08 2014 12 06 16 PM compressor
Figure: Good example - create the first bug (unfortunately bug has to be created manually)

Drew Robson
Chris Briggs
We open source. Powered by GitHub