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.
Baseline is helpful to ensure that your systems operate as expected. It's good to be able to track what has change since the resources were first deployed. Azure Resource Manager, or ARM, allows us to use JSON files called ARM templates to define resources in Azure. This template uses what's described as declarative syntax, rather than scripts. That allows us to repeatedly deploy resources with great consistency, and allows us to determine if the resources have changed from their original state. Declarative syntax means you define what the resources look like, and their dependencies between the resources. And the Azure Resource Manager takes care of the actual deployment. With a template, you can use Desired State Configuration packages, or DSC. These packages are the same within the operating system.
You can define a declarative configuration, and the provider takes care of ensuring the operating system looks like what you have defined. This style of configuration is often referred to as infrastructure as code. A benefit of using this method is the configuration code can be submitted to a version control system, to ensure that the changes are tracked and improved. This is in contrast to using scripts that execute command line operations in batches. Another approach can be to use change tracking. Change tracking is a solution that could be added to Azure resources, and works by using Log Analytics and the Azure Automation account. You can enable this on a virtual machine. Once this feature is enabled, I took these logs that collected to Log Analytics, and analyzed. And a dashboard was created to help identify changes and events to the operating system. The screenshot here shows Windows services and software have changed on this operating system.
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.