Join Mike Benkovich for an in-depth discussion in this video Debugging app services, part of Azure Enterprise Development: 2 Application Services.
- [Instructor] What to do when things go wrong.…In running our apps inside of Azure,…we need to have some sort of visibility…to be able to see what's going on…when the unexpected happens,…and fortunately, as we saw,…the Azure portal has a number of features,…including streaming logs,…that makes this possible.…There's also the actual process…that runs your app service called Kudu,…and we can investigate with that.…We can actually open up Kudu…and dive into it…and get the code information,…be able to see the process.…And if we need to,…we could go as deep as doing some remote debugging…with Visual Studio.…
What Kudu is is it's the engine behind the features…that run the app service…Anytime you have a app service,…you'll always have an extra scm as the link…on how you get to the Kudu environment.…So if you browse out to myapp.scm.azurewebsites.net,…then you'll be able to see exactly what that looks like.…This is the part where we can see the service settings,…all the files,…and much more.…Kudu also exposes the WebHooks,…
Learn how to provision new application services, set up autoscaling and deployment options, and use the different application types. Software architect and former Microsoft evangelist Mike Benkovich reviews options such as Continuous Delivery and DevOps Projects, Mobile Apps, and Logic Apps, which connect your applications to business-critical software such as Salesforce, Office 365, Dropbox, and more. He also shows how to stay on top of behavior and performance issues with Azure monitoring tools (including the powerful Application Insights feature), and debug any issues that arise.
- Provisioning application services
- Scaling and deployment options
- Developing for DevOps
- Developing with Mobile Apps and Logic Apps
- Monitoring Azure applications
- Debugging Azure applications