When you inherit an existing brownfield application, there are usually plenty of challenges to be tackled. The past year and a half, I have been assisting a team in “keeping the application from burning down”.
Often this results in:
- Customer support tickets “The application is slow”.
- Graphs like the one below.
Up until some point the team simply restarted the compute and reported ‘solved’. But as we all know, this doesn’t fix issues in the long term, so issues needed to be tackled.
There were plenty of specific samples, many of which I can’t share yet at this time due to the risk they might bring to the business. However we do have some tools at hand to spot and troubleshoot them on Azure (App Service). The coming series will show some tips and tricks to get started.
- Instance-Level View: Not All Servers Are Equal
- Diagnose and solve problems: the help of AI (App Insights)
- Code optimizations for deep insights
- Scaling to reduce cost
- Why do all requests show with a 1 minute duration
I’m updating the list as I add new posts.