The course is part of these learning paths
Azure Advisor Cost Recommendations
Monitoring Cost Consumption
Cost Management Report
This course looks into how to capture log data and metrics from Azure services and feed this information into different locations for processing. We take a look at diagnostic logging which can help to troubleshoot services and create queries and alerts based on that data. We also look into Azure Adviser, cost consumption reporting and how we can baseline resources. This aims to be an introduction to these advanced areas of Azure services.
- Understand how to use and configure diagnostic logging for Azure services
- Gain an understanding of Azure Monitor and how to create and manage alerts
- Review cost consumption reporting and how to create scheduled reports
- Investigate different methods for baselining resources
- People who want to become Azure cloud architects
- People preparing for Microsoft’s AZ-100 or AZ-300 exam
- General knowledge of Azure services
For more MS Azure-related training content, visit our dedicated MS Azure Training Library.
For this exercise we are going to set up diagnostic logging on a network security group, exploring all three export options and the different methods to configure them. This is a prerequisites video so we are going to go through what we need to have in place and set up the destinations. Here I have a resource group called Jenkins and I've used an Azure Marketplace template to deploy a Jenkins instance. So we have a Linux virtual machine and a Windows 2016 server. This is deployed both a jenkins-nsg and a windemo-nsg. From here we are going to create the objects in another resource group here called the AzureDiagnostics.
So I've created already. And we're gonna add the resources we need here to do our diagnostic logging. So first things first, let's go and create the OMS or Log Analytics workspace. Log analytics, and we'll click create. Not a lot of parameters here. I'll pause the video and come back in a second. So we've given it a name and selected the appropriate subscription. We've selected the existing resource group we've created and location, pricing tier free. With the OMS deployment, you cannot navigate away until this window’s finished validating. So this needs to finish its process before you can do the next thing. So we can see that validation succeeded and the deployment was successful. So if we go back to the resource group we can now see the AzureDiagnostics OMS, instance. Next, we will create the event hub. So we've given it a name, selected a pricing tier, basic.
Got the subscription and resource group and a location. We'll click create. Now this job is submitted to Azure resource manager and we can continue to do the next thing. So the last thing we need is a storage account. And create. So we've chosen the resource group, we've given the storage account a name, that's lowercase. The account kind, we need to make general purpose V1. The other options don't matter at this stage. So we're just going to do review and create. And create. Your deployment is underway and we can go look at the resource group. We can see that our Event Hub Namespace is there. OMS workspace is here and if we just give it a moment we can see the deploying storage account and we'll look for that success. And here we can see the success of that account. And now we have our three prerequisites for logging. Event hub, storage account, and an OMS workspace.
About the Author
Matthew Quickenden is a motivated Infrastructure Consultant with over 20 years of industry experience supporting Microsoft systems and other Microsoft products and solutions. He works as a technical delivery lead managing resources, understanding and translating customer requirements and expectations into architecture, and building technical solutions. In recent years, Matthew has been focused on helping businesses consume and utilize cloud technologies with a focus on leveraging automation to rapidly deploy and manage cloud resources at scale.