Having the ability to identify clear root cause for incidents in production workloads is valuable, the best way to prevent future incidents is to understand what caused past ones. Of course you can have a good set of load tests but still, incidents in production environments can happen and it’s crucial to have available data that can help to understand what happened so application can be improved and prevent replications. By LuisLopes.
In this article we will learn how to use Application Insights and automatic profiler to find root cause for past incidents and prepare logging platform to ensure meaningful data for analysis. The guide goes over:
- Check configuration
- Isolate relevant data in a concrete scenario
- Finding the latency source
- Other tools
- Checking profiler trace using Windows Performance Analyzer
Having the profiler option enabled in Application Insights is a great way to root cause past events without having to wait for problem to happen again to collect fresh data. Traces can be isolated, verified and changes applied avoiding future incidents. In this article is shown how to isolate relevant data in timeline, locate traces and use them to root cause analysis. Good read!
[Read More]