👉 Don't leave your teammates behind! See if anyone else needs a hand before you start a new challenge.
To bring our DevOps journey full circle we need to understand what is happening in our deployed environments. 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.
📚 Additional Reading
In this challenge we will look at some of the telemetry that has already been collected by our running instance and implement an outside availability test.
-
Review the
container-webapp-template.json
ARM template. Find where the Application Insights node was created and note how the Web App was configured to send its logs there.💡 Tips and Tricks
- Look for
Microsoft.Insights/components
in the ARM template. There is anapplicationId
that references the Web App
- Look for
-
Create a dashboard in the Azure Portal to provide a summary of the status of our site.
💡 Tips and Tricks
- Application Insights Overview dashboard: Application Dashboard
- Go to your app insights instance.
- Select "Application Dashboard" on the top left"
- Right click on your dashboard and select "Edit"
- On the right, you will see many different selections to choose a new tile. Select Metrics Chart and click Add
- A new tile will appear, save the dashboard
- Click on it to modify the metrics of that tile
- Set the scope to the production web app
- Select one of the options to reflect what the tile will represent such as number of connections
-
Implement an outside in availability test for the homepage of your site (hint)
💡 Tips and Tricks
- You should understand the importance of monitoring and some of the basic features offered by Application Insights.