Skip to content

Latest commit

 

History

History
27 lines (18 loc) · 3.04 KB

Challenge-08.md

File metadata and controls

27 lines (18 loc) · 3.04 KB
Raw

Challenge 08 - Azure Monitoring: Application Insights

< Previous Challenge - Home - Next Challenge >

Introduction

To bring our DevOps journey full circle we need to understand what is happening in our deployed sites. It is too late for us to find out about a problem, by the time our users are complaining about it. It is also imperative to know about not only the performance of the site, but also the impact positive or negative a feature has had on our users. Please take a moment to review the articles below to gain a better understanding of the importance of monitoring and Application Insights, one of the tools we have to make it easy in Azure.

  1. What is Monitoring?
  2. What is Application Insights?

Description

In this challenge we will look at some of the telemetry that has already been collected by our running instance. We will also link Application Insights to Azure DevOps. This will allow us to open work items in Azure Boards directly from Application Insights, ensuring that there is full traceability between the issue that happened and all the technical information about it to the work item that was created to ask the dev team to fix it, to the code that fixed the issue, to the build and release that saw that fix get deployed.

  • Review the container-webapp-template.json ARM template. Find where the Application Insights node was created and note how it the App Service Web Site was configured to send its logs there.
  • Create a dashboard in the Azure Portal to provide a summary of the status of our site. (Hint)
  • Implement an outside in availability test for the homepage of your site (Hint)
  • Link your Application Insights instance with your Azure Boards instance (Hint)
  • Using the failures feature of Application Insights find an exception that happened on your site. Using the link you created in the last step, open a work item to resolve that exception.

    NOTE: If your site doesn’t have any exceptions, you can create one easily by trying to go to a page that doesn’t exist. NOTE: It takes a min or two after an event happens for it to make its way to Application Insights and for it to be indexed so you can see it in the portal.

Success Criteria

  1. You should understand the importance of monitoring, some of the basic features offered by Application Insights, and the integration between Application Insights and Azure DevOps.

    NOTE: We are just scratching the surface of what is offered in Azure Monitoring, if you are interested in learning more there is a full What the Hack focused on Azure Monitoring.