Do you know why to use Application Insights?

Last updated by Vlad Kireyev [SSW] about 1 year ago.See history

Knowing the holistic health of your application is important once it has been deployed into production. Getting feedback on your Availability, errors, performance, and usage is an important part of DevOps. We recommend using Application Insights, as getting it set up and running is quick, simple and relatively painless.

Application Insights will tell you if your application goes down or runs slowly under load. If there are any uncaught exceptions, you'll be able to drill into the code to pinpoint the problem. You can also find out what your users are doing with the application so that you can tune it to their needs in each development cycle.

Google analytics
Figure: When developing a public website, you wouldn't deploy without Google Analytics to track metrics about user activity.

2020 03 24 15 27 26
Figure: For similar reasons, you shouldn't deploy a web application without metric tracking on performance and exceptions

  1. You need a portal for your app
  2. You need to know spikes are dangerous
  3. You need to monitor:

    1. Errors
    2. Performance
    3. Usage

r437355 2104314
Figure: Spikes on an Echidna are dangerous

sockeye daily count
Figure: Spikes on a graph are dangerous

To add Application Insights to your application, make sure you follow the rule Do you know how to set up Application Insights?

Can't use Application Insights? Check out the following rule Do you use the best exception handling library ?

We open source. Powered by GitHub