In this chapter, we discussed how to manage and supervise your ASP.NET Core web applications to help IT operations better understand what is happening during runtime, before and after errors occur.

We talked about the concept of logging, and how it can help reduce the time to understand and fix bugs. We illustrated different logging solutions: on-premises, in Microsoft Azure, in AWS, and in Docker.

You experienced how to configure logging in a Microsoft Azure environment using Azure App Service and Azure App Service Diagnostics, as well as the Azure Web Site Log Browser extension for log file analysis, in a detailed example.

You then saw how to do the same in AWS by accessing and downloading application logs, using AWS CloudWatch.

We then introduced the concepts of monitoring, and explained how to add monitoring to on-premises and Docker environments.

You configured Azure Application Insights to monitor your ASP.NET Core web applications in real time. You were even able to understand and solve the mystery behind the 404 Not Found problem.

In the last step, we showed you how to work with monitoring in an AWS environment, using AWS CloudWatch.

In the next chapter, we will…well, there is no next chapter. You have seen everything this book has to offer. We hope that you liked it and that you have found some value in understanding and assimilating the numerous examples we have given.

It is now up to you to create your own experiences, and to further improve your ASP.NET Core skills.

You can now start your journey as a veteran, as Nicolas Clerc (Cloud Architect, Microsoft France) has stated in his Foreword at the beginning of this book.

Good luck with that, and thank you for having taken the time to read the different chapters, and for having stayed with us for so long!