Application Monitoring and Alerting
Platform Monitoring and Alerting
The course is part of these learning paths
In this lesson, we will teach you about the four main priorities of Microsoft Azure: system monitoring, application monitoring, log monitoring, and alerting.
- System Monitoring: monitoring cloud resources and hardware
- Application Monitoring: instrumentation of your own service code
- Log Monitoring: analyzing logs generated by the system
- Alerting: the process of automating a variety of alarms triggered by your application
You will learn about three solutions provided by Azure to handle the priorities:
- System Monitoring: Azure Monitor service
- Application Monitoring: Application Insights service
- Log Monitoring: Azure Log Analytics
- Alerting: Application Insights service
For section 1 of this course we have four priorities: System monitoring, application monitoring, log monitoring, and alerting. System monitoring refers to monitoring of cloud resources and hardware with a focus on things like CPU, memory, and network. Application monitoring refers to instrumentation of your own service code - anything you deploy on top of your servers. Log monitoring, as you can probably guess, is focused on analyzing logs generated by your system. Finally alerting is the process by which we automate a variety of alarms triggered by your application getting into an unhealthy state. The fourth priority, alerting, is made possible by the first three - system and application monitoring along with log analysis.
For system monitoring you will need to learn about the Azure Monitor service. For logging you will get acquainted with Azure Log Analytics. For application monitoring Azure offers its Application Insights service, which we will also be using for alerting in the last part of the section. So if you’re ready, we’ll get started now in the next lesson with an introduction to Azure Monitor.
Jonathan Bethune is a senior technical consultant working with several companies including TopTal, BCG, and Instaclustr. He is an experienced devops specialist, data engineer, and software developer. Jonathan has spent years mastering the art of system automation with a variety of different cloud providers and tools. Before he became an engineer, Jonathan was a musician and teacher in New York City. Jonathan is based in Tokyo where he continues to work in technology and write for various publications in his free time.